v1.1
- About MogDB
- MogDB Introduction
- Comparison Between MogDB and openGauss
- MogDB Release Note
- High Availability and Performance
- Open Source Components
- Usage Limitations
- Terms of Use
- Quick Start
- Installation Guide
- Container Installation
- Standard Installation
- Installation Overview
- Preparing for Installation
- Installing the MogDB
- Verifying the Installation
- Uninstalling the MogDB
- Administrator Guide
- Routine Maintenance
- Primary and Standby Management
- MogHA Management
- MOT Engine
- Introducing MOT
- Using MOT
- Concepts of MOT
- Appendix
- Column-store Tables Management
- Backup and Restoration
- Importing and Exporting Data
- Importing Data
- Exporting Data
- Upgrade Guide
- Common Fault Locating Cases
- Core Fault Locating
- When the TPC-C is running and a disk to be injected is full, the TPC-C stops responding
- Standby Node in the Need Repair (WAL) State
- Insufficient Memory
- Service Startup Failure
- "Error:No space left on device" Is Displayed
- 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
- File Is Damaged in the XFS File System
- Primary Node Is Hung in Demoting During a Switchover
- Disk Space Usage Reaches the Threshold and the Database Becomes Read-only
- Slow Response to a Query Statement
- Analyzing the Status of a Query Statement
- Forcibly Terminating a Session
- Analyzing Whether a Query Statement Is Blocked
- Low Query Efficiency
- "Lock wait timeout" Is Displayed When a User Executes an SQL Statement
- Table Size Does not Change After VACUUM FULL Is Executed on the Table
- An Error Is Reported When the Table Partition Is Modified
- Different Data Is Displayed for the Same Table Queried By Multiple Users
- When a User Specifies Only an Index Name to Modify the Index, A Message Indicating That the Index Does Not Exist Is Displayed
- Reindexing Fails
- An Error Occurs During Integer Conversion
- "too many clients already" Is Reported or Threads Failed To Be Created in High Concurrency Scenarios
- B-tree Index Faults
- Security Guide
- Database Security Management
- Performance Tuning
- System Optimization
- SQL Optimization
- WDR Snapshot Schema
- Developer Guide
- Application Development Guide
- Development Specifications
- Development Based on JDBC
- Overview
- JDBC Package, Driver Class, and Environment Class
- Development Process
- Loading the Driver
- Connecting to a Database
- Connecting to the Database (Using SSL)
- Running SQL Statements
- Processing Data in a Result Set
- Closing a Connection
- Example: Common Operations
- Example: Retrying SQL Queries for Applications
- Example: Importing and Exporting Data Through Local Files
- Example 2: Migrating Data from a MY Database to MogDB
- Example: Logic Replication Code
- JDBC Interface Reference
- Development Based on ODBC
- Development Based on libpq
- Commissioning
- Appendices
- Stored Procedure
- User Defined Functions
- Application Development Guide
- Tool Reference
- System Catalogs and System Views
- Overview of System Catalogs and System Views
- System Catalogs
- GS_CLIENT_GLOBAL_KEYS
- GS_CLIENT_GLOBAL_KEYS_ARGS
- GS_COLUMN_KEYS
- GS_COLUMN_KEYS_ARGS
- GS_ENCRYPTED_COLUMNS
- GS_OPT_MODEL
- GS_WLM_INSTANCE_HISTORY
- GS_WLM_OPERATOR_INFO
- GS_WLM_PLAN_ENCODING_TABLE
- GS_WLM_PLAN_OPERATOR_INFO
- GS_WLM_USER_RESOURCE_HISTORY
- PG_AGGREGATE
- PG_AM
- PG_AMOP
- PG_AMPROC
- PG_APP_WORKLOADGROUP_MAPPING
- PG_ATTRDEF
- PG_ATTRIBUTE
- PG_AUTHID
- PG_AUTH_HISTORY
- PG_AUTH_MEMBERS
- PG_CAST
- PG_CLASS
- PG_COLLATION
- PG_CONSTRAINT
- PG_CONVERSION
- PG_DATABASE
- PG_DB_ROLE_SETTING
- PG_DEFAULT_ACL
- PG_DEPEND
- PG_DESCRIPTION
- PG_DIRECTORY
- PG_ENUM
- PG_EXTENSION
- PG_EXTENSION_DATA_SOURCE
- PG_FOREIGN_DATA_WRAPPER
- PG_FOREIGN_SERVER
- PG_FOREIGN_TABLE
- PG_INDEX
- PG_INHERITS
- PG_JOB
- PG_JOB_PROC
- PG_LANGUAGE
- PG_LARGEOBJECT
- PG_LARGEOBJECT_METADATA
- PG_NAMESPACE
- PG_OBJECT
- PG_OPCLASS
- PG_OPERATOR
- PG_OPFAMILY
- PG_PARTITION
- PG_PLTEMPLATE
- PG_PROC
- PG_RANGE
- PG_RESOURCE_POOL
- PG_REWRITE
- PG_RLSPOLICY
- PG_SECLABEL
- PG_SHDEPEND
- PG_SHDESCRIPTION
- PG_SHSECLABEL
- PG_STATISTIC
- PG_STATISTIC_EXT
- PG_TABLESPACE
- PG_TRIGGER
- PG_TS_CONFIG
- PG_TS_CONFIG_MAP
- PG_TS_DICT
- PG_TS_PARSER
- PG_TS_TEMPLATE
- PG_TYPE
- PG_USER_MAPPING
- PG_USER_STATUS
- PG_WORKLOAD_GROUP
- PLAN_TABLE_DATA
- STATEMENT_HISTORY
- System Views
- GS_SESSION_CPU_STATISTICS
- GS_SESSION_MEMORY_STATISTICS
- GS_SQL_COUNT
- GS_WLM_OPERATOR_HISTORY
- GS_WLM_OPERATOR_STATISTICS
- GS_WLM_PLAN_OPERATOR_HISTORY
- GS_WLM_REBUILD_USER_RESOURCE_POOL
- GS_WLM_RESOURCE_POOL
- GS_WLM_SESSION_HISTORY
- GS_WLM_SESSION_INFO_ALL
- GS_WLM_USER_INFO
- GS_WLM_SESSION_STATISTICS
- GS_STAT_SESSION_CU
- MPP_TABLES
- PG_AVAILABLE_EXTENSION_VERSIONS
- PG_AVAILABLE_EXTENSIONS
- PG_CURSORS
- PG_EXT_STATS
- PG_GET_INVALID_BACKENDS
- PG_GET_SENDERS_CATCHUP_TIME
- PG_GROUP
- PG_GTT_RELSTATS
- PG_GTT_STATS
- PG_GTT_ATTACHED_PIDS
- PG_INDEXES
- PG_LOCKS
- PG_MATVIEWS
- PG_NODE_ENV
- PG_OS_THREADS
- PG_PREPARED_STATEMENTS
- PG_PREPARED_XACTS
- PG_REPLICATION_SLOTS
- PG_RLSPOLICIES
- PG_ROLES
- PG_RULES
- PG_SECLABELS
- PG_SESSION_WLMSTAT
- PG_SESSION_IOSTAT
- PG_SETTINGS
- PG_SHADOW
- PG_STATS
- PG_STAT_ACTIVITY
- PG_STAT_ALL_INDEXES
- PG_STAT_ALL_TABLES
- PG_STAT_BAD_BLOCK
- PG_STAT_BGWRITER
- PG_STAT_DATABASE
- PG_STAT_DATABASE_CONFLICTS
- PG_STAT_USER_FUNCTIONS
- PG_STAT_USER_INDEXES
- PG_STAT_USER_TABLES
- PG_STAT_REPLICATION
- PG_STAT_SYS_INDEXES
- PG_STAT_SYS_TABLES
- PG_STAT_XACT_ALL_TABLES
- PG_STAT_XACT_SYS_TABLES
- PG_STAT_XACT_USER_FUNCTIONS
- PG_STAT_XACT_USER_TABLES
- 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
- PG_THREAD_WAIT_STATUS
- PG_TABLES
- PG_TDE_INFO
- PG_TIMEZONE_NAMES
- PG_TOTAL_USER_RESOURCE_INFO
- PG_USER
- PG_USER_MAPPINGS
- PG_VIEWS
- PG_WLM_STATISTICS
- PLAN_TABLE
- GS_FILE_STAT
- GS_OS_RUN_INFO
- GS_REDO_STAT
- GS_SESSION_MEMORY
- GS_SESSION_MEMORY_DETAIL
- GS_SESSION_STAT
- GS_SESSION_TIME
- GS_THREAD_MEMORY_DETAIL
- GS_TOTAL_MEMORY_DETAIL
- PG_TIMEZONE_ABBREVS
- PG_TOTAL_USER_RESOURCE_INFO_OID
- PG_VARIABLE_INFO
- GS_INSTANCE_TIME
- Functions and Operators
- Logical Operators
- Comparison Operators
- Character Processing Functions and Operators
- Binary String Functions and Operators
- Bit String Functions and Operators
- Mode Matching Operators
- Mathematical Functions and Operators
- Date and Time Processing Functions and Operators
- Type Conversion Functions
- Geometric Functions and Operators
- Network Address Functions and Operators
- Text Search Functions and Operators
- JSON Functions
- SEQUENCE Functions
- Array Functions and Operators
- Range Functions and Operators
- Aggregate Functions
- Window Functions
- Security Functions
- Encrypted Equality Functions
- Set Returning Functions
- Conditional Expression Functions
- System Information Functions
- System Administration Functions
- Statistics Information Functions
- Trigger Functions
- Global Temporary Table Functions
- AI Feature Functions
- Other System Functions
- Supported Data Types
- SQL Syntax
- ABORT
- ALTER DATABASE
- ALTER DATA SOURCE
- ALTER DEFAULT PRIVILEGES
- ALTER DIRECTORY
- ALTER FOREIGN TABLE
- ALTER FUNCTION
- ALTER GROUP
- ALTER INDEX
- ALTER LARGE OBJECT
- ALTER MATERIALIZED VIEW
- ALTER ROLE
- ALTER ROW LEVEL SECURITY POLICY
- ALTER RULE
- ALTER SCHEMA
- ALTER SEQUENCE
- ALTER SERVER
- ALTER SESSION
- ALTER SYNONYM
- ALTER SYSTEM KILL SESSION
- ALTER SYSTEM SET
- ALTER TABLE
- ALTER TABLE PARTITION
- ALTER TABLESPACE
- ALTER TEXT SEARCH CONFIGURATION
- ALTER TEXT SEARCH DICTIONARY
- ALTER TRIGGER
- ALTER TYPE
- ALTER USER
- ALTER USER MAPPING
- ALTER VIEW
- ANALYZE | ANALYSE
- BEGIN
- CALL
- CHECKPOINT
- CLOSE
- CLUSTER
- COMMENT
- COMMIT | END
- COMMIT PREPARED
- COPY
- CREATE CLIENT MASTER KEY
- CREATE COLUMN ENCRYPTION KEY
- CREATE DATABASE
- CREATE DATA SOURCE
- CREATE DIRECTORY
- CREATE FOREIGN TABLE
- CREATE FUNCTION
- CREATE GROUP
- CREATE INDEX
- CREATE MATERIALIZED VIEW
- CREATE ROW LEVEL SECURITY POLICY
- CREATE PROCEDURE
- CREATE ROLE
- CREATE RULE
- CREATE SCHEMA
- CREATE SEQUENCE
- CREATE SERVER
- CREATE SYNONYM
- CREATE TABLE
- CREATE TABLE AS
- CREATE TABLE PARTITION
- CREATE TABLESPACE
- CREATE TEXT SEARCH CONFIGURATION
- CREATE TEXT SEARCH DICTIONARY
- CREATE TRIGGER
- CREATE TYPE
- CREATE USER
- CREATE USER MAPPING
- CREATE VIEW
- CURSOR
- DEALLOCATE
- DECLARE
- DELETE
- DO
- DROP CLIENT MASTER KEY
- DROP COLUMN ENCRYPTION KEY
- DROP DATABASE
- DROP DATA SOURCE
- DROP DIRECTORY
- DROP FOREIGN TABLE
- DROP FUNCTION
- DROP GROUP
- DROP INDEX
- DROP MATERIALIZED VIEW
- DROP OWNED
- DROP ROW LEVEL SECURITY POLICY
- DROP PROCEDURE
- DROP ROLE
- DROP RULE
- DROP SCHEMA
- DROP SEQUENCE
- DROP SERVER
- DROP SYNONYM
- DROP TABLE
- DROP TABLESPACE
- DROP TEXT SEARCH CONFIGURATION
- DROP TEXT SEARCH DICTIONARY
- DROP TRIGGER
- DROP TYPE
- DROP USER
- DROP USER MAPPING
- DROP VIEW
- EXECUTE
- EXPLAIN
- EXPLAIN PLAN
- FETCH
- GRANT
- INSERT
- LOCK
- MOVE
- MERGE INTO
- PREPARE
- PREPARE TRANSACTION
- REASSIGN OWNED
- REFRESH MATERIALIZED VIEW
- REINDEX
- RELEASE SAVEPOINT
- RESET
- REVOKE
- ROLLBACK
- ROLLBACK PREPARED
- ROLLBACK TO SAVEPOINT
- SAVEPOINT
- SELECT
- SELECT INTO
- SET
- SET CONSTRAINTS
- SET ROLE
- SET SESSION AUTHORIZATION
- SET TRANSACTION
- SHOW
- SHUTDOW
- START TRANSACTION
- TRUNCATE
- UPDATE
- VACUUM
- VALUES
- GUC Parameters
- GUC Parameter Usage
- File Location
- Connection and Authentication
- Resource Consumption
- Parallel Import
- Write Ahead Log
- HA Replication
- Memory Table
- Query Planning
- Error Reporting and Logging
- Alarm Detection
- Statistics During the Database Running
- Load Management
- Automatic Vacuuming
- Default Settings of Client Connection
- Lock Management
- Version and Platform Compatibility
- Faut Tolerance
- Connection Pool Parameters
- MogDB Transaction
- Developer Options
- Auditing
- Upgrade Parameters
- Miscellaneous Parameters
- Wait Events
- Query
- System Performance Snapshot
- Equality Query in a Fully-encrypted Database
- Global Temporary Table
- Appendix
- DBE_PERF
- DBE_PERF Overview
- OS
- Instance
- Memory
- File
- Object
- STAT_USER_TABLES
- SUMMARY_STAT_USER_TABLES
- GLOBAL_STAT_USER_TABLES
- STAT_USER_INDEXES
- SUMMARY_STAT_USER_INDEXES
- GLOBAL_STAT_USER_INDEXES
- STAT_SYS_TABLES
- SUMMARY_STAT_SYS_TABLES
- GLOBAL_STAT_SYS_TABLES
- STAT_SYS_INDEXES
- SUMMARY_STAT_SYS_INDEXES
- GLOBAL_STAT_SYS_INDEXES
- STAT_ALL_TABLES
- SUMMARY_STAT_ALL_TABLES
- GLOBAL_STAT_ALL_TABLES
- STAT_ALL_INDEXES
- SUMMARY_STAT_ALL_INDEXES
- GLOBAL_STAT_ALL_INDEXES
- STAT_DATABASE
- SUMMARY_STAT_DATABASE
- GLOBAL_STAT_DATABASE
- STAT_DATABASE_CONFLICTS
- SUMMARY_STAT_DATABASE_CONFLICTS
- GLOBAL_STAT_DATABASE_CONFLICTS
- STAT_XACT_ALL_TABLES
- SUMMARY_STAT_XACT_ALL_TABLES
- GLOBAL_STAT_XACT_ALL_TABLES
- STAT_XACT_SYS_TABLES
- SUMMARY_STAT_XACT_SYS_TABLES
- GLOBAL_STAT_XACT_SYS_TABLES
- STAT_XACT_USER_TABLES
- SUMMARY_STAT_XACT_USER_TABLES
- GLOBAL_STAT_XACT_USER_TABLES
- STAT_XACT_USER_FUNCTIONS
- SUMMARY_STAT_XACT_USER_FUNCTIONS
- GLOBAL_STAT_XACT_USER_FUNCTIONS
- STAT_BAD_BLOCK
- SUMMARY_STAT_BAD_BLOCK
- GLOBAL_STAT_BAD_BLOCK
- STAT_USER_FUNCTIONS
- SUMMARY_STAT_USER_FUNCTIONS
- GLOBAL_STAT_USER_FUNCTIONS
- Workload
- Session/Thread
- SESSION_STAT
- GLOBAL_SESSION_STAT
- SESSION_TIME
- GLOBAL_SESSION_TIME
- SESSION_MEMORY
- GLOBAL_SESSION_MEMORY
- SESSION_MEMORY_DETAIL
- GLOBAL_SESSION_MEMORY_DETAIL
- SESSION_STAT_ACTIVITY
- GLOBAL_SESSION_STAT_ACTIVITY
- THREAD_WAIT_STATUS
- GLOBAL_THREAD_WAIT_STATUS
- LOCAL_THREADPOOL_STATUS
- GLOBAL_THREADPOOL_STATUS
- SESSION_CPU_RUNTIME
- SESSION_MEMORY_RUNTIME
- STATEMENT_IOSTAT_COMPLEX_RUNTIME
- Transaction
- Query
- STATEMENT
- SUMMARY_STATEMENT
- STATEMENT_COUNT
- GLOBAL_STATEMENT_COUNT
- SUMMARY_STATEMENT_COUNT
- GLOBAL_STATEMENT_COMPLEX_HISTORY
- GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE
- GLOBAL_STATEMENT_COMPLEX_RUNTIME
- STATEMENT_RESPONSETIME_PERCENTILE
- STATEMENT_USER_COMPLEX_HISTORY
- STATEMENT_COMPLEX_RUNTIME
- STATEMENT_COMPLEX_HISTORY_TABLE
- STATEMENT_COMPLEX_HISTORY
- STATEMENT_WLMSTAT_COMPLEX_RUNTIME
- STATEMENT_HISTORY
- Cache/IO
- STATIO_USER_TABLES
- SUMMARY_STATIO_USER_TABLES
- GLOBAL_STATIO_USER_TABLES
- STATIO_USER_INDEXES
- SUMMARY_STATIO_USER_INDEXES
- GLOBAL_STATIO_USER_INDEXES
- STATIO_USER_SEQUENCES
- SUMMARY_STATIO_USER_SEQUENCES
- GLOBAL_STATIO_USER_SEQUENCES
- STATIO_SYS_TABLES
- SUMMARY_STATIO_SYS_TABLES
- GLOBAL_STATIO_SYS_TABLES
- STATIO_SYS_INDEXES
- SUMMARY_STATIO_SYS_INDEXES
- GLOBAL_STATIO_SYS_INDEXES
- STATIO_SYS_SEQUENCES
- SUMMARY_STATIO_SYS_SEQUENCES
- GLOBAL_STATIO_SYS_SEQUENCES
- STATIO_ALL_TABLES
- SUMMARY_STATIO_ALL_TABLES
- GLOBAL_STATIO_ALL_TABLES
- STATIO_ALL_INDEXES
- SUMMARY_STATIO_ALL_INDEXES
- GLOBAL_STATIO_ALL_INDEXES
- STATIO_ALL_SEQUENCES
- SUMMARY_STATIO_ALL_SEQUENCES
- GLOBAL_STATIO_ALL_SEQUENCES
- GLOBAL_STAT_DB_CU
- GLOBAL_STAT_SESSION_CU
- Utility
- REPLICATION_STAT
- GLOBAL_REPLICATION_STAT
- REPLICATION_SLOTS
- GLOBAL_REPLICATION_SLOTS
- BGWRITER_STAT
- GLOBAL_BGWRITER_STAT
- GLOBAL_CKPT_STATUS
- GLOBAL_DOUBLE_WRITE_STATUS
- GLOBAL_PAGEWRITER_STATUS
- GLOBAL_RECORD_RESET_TIME
- GLOBAL_REDO_STATUS
- GLOBAL_RECOVERY_STATUS
- CLASS_VITAL_INFO
- USER_LOGIN
- SUMMARY_USER_LOGIN
- GLOBAL_GET_BGWRITER_STATUS
- Lock
- Wait Events
- Configuration
- Operator
- Workload Manager
- Global Plancache
- Appendix
- Error Code Reference
- Description of SQL Error Codes
- Third-Party Library Error Codes
- GAUSS-00001 - GAUSS-00100
- GAUSS-00101 - GAUSS-00200
- GAUSS 00201 - GAUSS 00300
- GAUSS 00301 - GAUSS 00400
- GAUSS 00401 - GAUSS 00500
- GAUSS 00501 - GAUSS 00600
- GAUSS 00601 - GAUSS 00700
- GAUSS 00701 - GAUSS 00800
- GAUSS 00801 - GAUSS 00900
- GAUSS 00901 - GAUSS 01000
- GAUSS 01001 - GAUSS 01100
- GAUSS 01101 - GAUSS 01200
- GAUSS 01201 - GAUSS 01300
- GAUSS 01301 - GAUSS 01400
- GAUSS 01401 - GAUSS 01500
- GAUSS 01501 - GAUSS 01600
- GAUSS 01601 - GAUSS 01700
- GAUSS 01701 - GAUSS 01800
- GAUSS 01801 - GAUSS 01900
- GAUSS 01901 - GAUSS 02000
- GAUSS 02001 - GAUSS 02100
- GAUSS 02101 - GAUSS 02200
- GAUSS 02201 - GAUSS 02300
- GAUSS 02301 - GAUSS 02400
- GAUSS 02401 - GAUSS 02500
- GAUSS 02501 - GAUSS 02600
- GAUSS 02601 - GAUSS 02700
- GAUSS 02701 - GAUSS 02800
- GAUSS 02801 - GAUSS 02900
- GAUSS 02901 - GAUSS 03000
- GAUSS 03001 - GAUSS 03100
- GAUSS 03101 - GAUSS 03200
- GAUSS 03201 - GAUSS 03300
- GAUSS 03301 - GAUSS 03400
- GAUSS 03401 - GAUSS 03500
- GAUSS 03501 - GAUSS 03600
- GAUSS 03601 - GAUSS 03700
- GAUSS 03701 - GAUSS 03800
- GAUSS 03801 - GAUSS 03900
- GAUSS 03901 - GAUSS 04000
- GAUSS 04001 - GAUSS 04100
- GAUSS 04101 - GAUSS 04200
- GAUSS 04201 - GAUSS 04300
- GAUSS 04301 - GAUSS 04400
- GAUSS 04401 - GAUSS 04500
- GAUSS 04501 - GAUSS 04600
- GAUSS 04601 - GAUSS 04700
- GAUSS 04701 - GAUSS 04800
- GAUSS 04801 - GAUSS 04900
- GAUSS 04901 - GAUSS 05000
- GAUSS 05001 - GAUSS 05100
- GAUSS 05101 - GAUSS 05200
- GAUSS 05201 - GAUSS 05300
- GAUSS 05301 - GAUSS 05400
- GAUSS 05401 - GAUSS 05500
- GAUSS 05501 - GAUSS 05600
- GAUSS 05601 - GAUSS 05700
- GAUSS 05701 - GAUSS 05800
- GAUSS 05801 - GAUSS 05900
- GAUSS 05901 - GAUSS 06000
- GAUSS 06001 - GAUSS 06100
- GAUSS 06101 - GAUSS 06200
- GAUSS 06201 - GAUSS 06300
- GAUSS 06301 - GAUSS 06400
- GAUSS 06401 - GAUSS 06500
- GAUSS 06501 - GAUSS 06600
- GAUSS 06601 - GAUSS 06700
- GAUSS 06701 - GAUSS 06800
- GAUSS 06801 - GAUSS 06900
- GAUSS 06901 - GAUSS 07000
- GAUSS 07001 - GAUSS 07100
- GAUSS 07101 - GAUSS 07200
- GAUSS 07201 - GAUSS 07300
- GAUSS 07301 - GAUSS 07400
- GAUSS 07401 - GAUSS 07480
- GAUSS 50000 - GAUSS 50999
- GAUSS 51000 - GAUSS 51999
- GAUSS 52000 - GAUSS 52999
- GAUSS 53000 - GAUSS 53699
- System Catalogs and System Views
- Glossary
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 | Client Master Key. |
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. |
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 MogDB 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 MogDB 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 Postgres. 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. MogDB 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 | MogDB interaction terminal. It enables you to interactively enter and issue queries to MogDB, 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. |
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. MogDB 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 MogDB 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 MogDB. 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. |
KMC | Acronym for key management component. |
KMS | Acronym for key management service. |
KSF | Acronym for key store file. |
K - O | |
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 MogDB 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, MogDB 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 MogDB. The default size of a page is 8 KB. |
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. |
SLES | Acronym for SUSE Linux enterprise server, an enterprise Linux OS provided by SUSE. |
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. |
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 MogDB 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 MogDB and files controlled by the process. MogDB allows multiple database instances to be installed on one physical node. A database instance is also called a logical node. |
database primary/standby solution | MogDB provides a highly reliable HA solution. In this solution, each MogDB is called a primary or standby node. At the same time, only one MogDB 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 | |
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 MogDB, 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 comprised 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 MogDB 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 MogDB 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 MogDB to ensure data consistency. During startup, MogDB 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. |