v2.1

About MogDB
- MogDB Introduction
- Comparison Between MogDB and openGauss
- MogDB Release Notes
  - MogDB 2.1.1
  - MogDB 2.1.0
- Open Source Components
- Usage Limitations
- Terms of Use
Quick Start
- MogDB Playground
- Container-based MogDB Installation
- Installation on a Single Node
- MogDB Access
  - Use CLI to Access MogDB
    - gsql
    - pgcli
  - Use GUI to Access MogDB
    - Data Studio
    - DBeaver
  - Use Middleware to Access MogDB
    - Use WebLogic to Configure MogDB Data Sources
    - Use WebSphere to Configure MogDB Data Sources
  - Use Programming Language to Access MogDB
    - Java
    - C/C++
    - Python
    - Go
    - Rust
    - NodeJS
- Using Sample Dataset Mogila
Characteristic Description
Installation Guide
- Container Installation
- Simplified Installation Process
- Standard Installation
  - Installation Overview
  - Preparing for Installation
    - Environment Requirement
    - Modifying OS Configuration
  - Installing MogDB
  - Verifying the Installation
  - Recommended Parameter Settings
  - Uninstalling MogDB
- Manual Installation
Administrator Guide
AI Features Guide
- Overview
- Predictor: AI Query Time Forecasting
- X-Tuner: Parameter Optimization and Diagnosis
- SQLdiag: Slow SQL Discovery
- A-Detection: Status Monitoring
- Index-advisor: Index Recommendation
- DeepSQL
- AI-Native Database (DB4AI)
Security Guide
- Database Security Management
Developer Guide
- Application Development Guide
  - Development Specifications
  - Development Based on JDBC
  - Development Based on ODBC
  - Development Based on libpq
    - Development Based on libpq
    - libpq API Reference
      - Database Connection Control Functions
        Description
        PQconnectdbParams
        PQconnectdb
        PQconninfoParse
        PQconnectStart
        PQerrorMessage
        PQsetdbLogin
        PQfinish
        PQreset
        PQstatus
      - Database Statement Execution Functions
        PQclear
        PQexec
        PQexecParams
        PQexecParamsBatch
        PQexecPrepared
        PQexecPreparedBatch
        PQfname
        PQgetvalue
        PQnfields
        PQntuples
        PQprepare
        PQresultStatus
      - Functions for Asynchronous Command Processing
        Description
        PQsendQuery
        PQsendQueryParams
        PQsendPrepare
        PQsendQueryPrepared
        PQflush
      - Functions for Canceling Queries in Progress
        PQgetCancel
        PQfreeCancel
        PQcancel
      - Example
      - Connection Characters
  - Psycopg-Based Development
  - Commissioning
  - Appendices
- Stored Procedure
- User Defined Functions
- PL/pgSQL-SQL Procedural Language
- Scheduled Jobs
  - PKG_SERVICE API
- Autonomous Transaction
- Logical Replication
  - Logical Decoding
    - Overview
    - Logical Decoding by SQL Function Interfaces
- Foreign Data Wrapper
- Materialized View
  - Materialized View Overview
  - Full Materialized View
  - Incremental Materialized View
- Resource Load Management
  - Overview
  - Resource Management Preparation
Performance Tuning Guide
Reference Guide
Common Faults and Identification Guide
- Common Fault Locating Methods
- Common Fault Locating Cases
  - Core Fault Locating
  - Permission/Session/Data Type Fault Location
  - Service/High Availability/Concurrency Fault Location
  - Table/Partition Table Fault Location
    - Table Size Does not Change After VACUUM FULL Is Executed on the Table
    - An Error Is Reported When the Table Partition Is Modified
  - File System/Disk/Memory Fault Location
  - SQL Fault Location
  - Index Fault Location
Source Code Parsing
FAQs
Glossary

Starting and Stopping MogDB

Starting MogDB

Log in as the OS user omm to the primary node of the database.
Run the following command to start MogDB:
```
gs_om -t start
```
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.

Stopping MogDB

Log in as the OS user omm to the primary node of the database.
Run the following command to stop MogDB:
```
gs_om -t stop
```
NOTE: For details about how to start and stop nodes and availability zones (AZs), see gs_om.

Examples

Start MogDB:

gs_om -t start
Starting cluster.
=========================================
=========================================
Successfully started.

Stop MogDB:

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.

If the startup fails due to timeout, you can run the following command to set the startup timeout interval, which is 300s by default:

gs_om -t start --time-out=300