v3.0

About MogDB
- MogDB Introduction
- Comparison Between MogDB and openGauss
- MogDB Release Notes
- 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
  - 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
    - .Net
- Using Sample Dataset Mogila
Characteristic Description
Installation Guide
- Installation Preparation
  - Environment Requirement
  - Operating System Configuration
- Container Installation
- PTK-based Installation
- OM-based Installation
- Manual Installation
- Recommended Parameter Settings
Administrator Guide
AI Features Guide
- AI Features Overview
- AI4DB: Autonomous Database O&M
  - DBMind Mode
  - Components that Support DBMind
    - Prometheus Exporter
  - AI Sub-functions of the DBMind
    - X-Tuner: Parameter Tuning and Diagnosis
    - Index-advisor: Index Recommendation
    - AI4DB: Root Cause Analysis for Slow SQL Statements
    - AI4DB: Trend Prediction
    - SQLdiag: Slow SQL Discovery
- DB4AI: Database-driven AI
  - Native DB4AI Engine
  - Full-process AI
    - PLPython Fenced Mode
    - DB4AI-Snapshots for Data Version Management
- AI in DB
  - Intelligence Explain: SQL Statement Query Time Prediction
Security Guide
- Database Security Management
Developer Guide
- Application Development Guide
  - Development Specifications
  - Development Based on JDBC
  - Development Based on ODBC
  - Development Based on libpq
    - Dependent Header Files of libpq
    - Development Process
    - Example
    - Link Parameters
    - 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
  - Psycopg-Based Development
  - Commissioning
- Stored Procedure
- User Defined Functions
- PL/pgSQL-SQL Procedural Language
  - Overview of PL/pgSQL Functions
  - Data Types
  - Data Type Conversion
  - Arrays and Records
  - DECLARE Syntax
  - Basic Statements
  - Dynamic Statements
  - Control Statements
  - Transaction Management
  - Other Statements
  - Cursors
  - Advanced Packages
    - Basic Interfaces
      - PKG_SERVICE
  - Retry Management
  - Debugging
  - package
- Scheduled Jobs
  - PKG_SERVICE API
- Autonomous Transaction
- Logical Replication
  - Logical Decoding
    - Overview
    - Logical Decoding by SQL Function Interfaces
  - Publication-Subscription
- Foreign Data Wrapper
- Materialized View
  - Materialized View Overview
  - Full Materialized View
  - Incremental Materialized View
- Partition Management
  - Partition Pruning
  - Recommendations For Choosing A Partitioning Strategy
Performance Tuning Guide
Reference Guide
Common Faults and Identification
- 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
Mogeaver
- Overview
- Release Notes

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.

Update table statistics.

Do ANALYZE to the product_info table.

ANALYZE product_info;

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.

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.