Database guides

openGauss

Updated 2026-08-11 · 2 min read

A PostgreSQL fork from Huawei, and the base of the commercial GaussDB. Speaks the PG wire protocol; AddisDB relaxes introspection for its older catalog.

openGauss is an open-source database forked from PostgreSQL 9.2 and developed largely by Huawei. It is also the foundation of the commercial GaussDB. It speaks the PostgreSQL wire protocol, so AddisDB connects with its Postgres driver.

Who it is for

openGauss is most common where a domestic-vendor database is a procurement requirement, particularly in China. It adds column-store tables, its own storage engine options and AI-assisted parameter tuning on top of the Postgres it came from.

Because the fork point is PostgreSQL 9.2, several catalog helpers that modern Postgres tooling assumes are either missing or shaped differently. AddisDB runs introspection leniently for openGauss: an optional catalog section that fails comes back empty instead of failing the whole schema load, so you get the tables and columns even where function or trigger definitions cannot be read.

Set up the server

  1. Note the host and port. openGauss commonly listens on 5432, though some distributions default to 26000 — check postgresql.conf for the port setting.
  2. The initial administrative user is usually omm.
  3. openGauss requires a password on first login and rejects the trust method for remote connections, so make sure the account you use has one set.
  4. Add your client address to pg_hba.conf with the sha256 method and reload.
# openGauss ships gsql, but any Postgres client works over the same protocol
gsql -h opengauss.example.com -p 5432 -U omm -d postgres -c 'SELECT version();'

Connect from AddisDB

  1. New Connection → openGauss. Port prefills to 5432, database to postgres and username to omm.
  2. Enter the host and password.
  3. Set SSL mode to require if the server is configured for TLS.
  4. Test, then Save.

What AddisDB gives you

Queries, the schema tree, in-grid editing, the structured create and alter table builders, database-user management and mock data all work — openGauss keeps PostgreSQL’s DDL and its role system.

Query plans use the standard PostgreSQL EXPLAIN with its full option list, including FORMAT JSON.

The Live Monitor is best-effort rather than guaranteed. openGauss has a pg_stat_activity, but its columns vary across releases, so AddisDB tries the standard queries and falls back to a clean unsupported panel if the server answers differently. You will either get real sessions or an honest empty state, never invented numbers.