Starting from version 3.7.0, GDOM (GBase Database Operation Manager) supports automatic deployment of PostgreSQL as its resource database, in addition to the existing MySQL support. This guide walks through a single‑node installation where PostgreSQL replaces MySQL as the metadata store for GDOM.
1. Configuration
Modify the demo.options file found in the extracted GDOM installation package. The key settings that switch the resource database to PostgreSQL are:
gdomDb=10.0.2.151
gdomDbPort=5432
gdomDbUser=gdom
gdomDbPwd=111111
gdomDbDriver=org.postgresql.Driver
gdomDbUrl=
A complete demo.options example for a single‑node deployment on 10.0.2.151:
gdomRoot=/opt/gdom
gdomService=10.0.2.151
gdomServicePort=8080
user=gdom
# Resource database (PostgreSQL)
gdomDb=10.0.2.151
gdomDbPort=5432
gdomDbUser=gdom
gdomDbPwd=111111
gdomDbDriver=org.postgresql.Driver
gdomDbUrl=
gdomDbHa=
gdomDbHaPort=3307
gdomDbHaMonitorPort=8811
gdomDbHaMonitorAdmin=admin
gdomDbHaMonitorPwd=admin
gdomGBaseDb=10.0.2.151
gdomGBaseDbPort=5268
gdomGBaseDbUser=gbase
gdomGBaseDbPwd=gbase
gdomGBaseDbUrl=
gdomNginx=10.0.2.151
gdomNginxPort=8810
gdomNginxUrl=
gdomRedis=10.0.2.151
gdomRedisPort=7481
gdomRedisDb=0
gdomRedisUrl=
gdomMq=10.0.2.151
gdomMqPort=9876
gdomDashBoardPort=9898
gdomMqUrl=
Security note: After a successful installation, the plain‑text passwords in
demo.optionsare no longer needed. Remove them to avoid accidental exposure. The application configuration files use encrypted passwords internally.
2. Installation
All steps start as the root user.
2.1 Mutual Trust Setup
Run the mutual trust script. It will create the gdom OS user and configure password‑less SSH.
[root@vm151 GDOM-v3.7.0-build3-redhat8-x86_64]# ./gdomMutualTrust.sh -a
...
10.0.2.151 gdom user mutual trust verification passed
Mutual trust for user gdom completed
2.2 Install Services
Switch to the gdom user and run the installation script. The script performs environment checks, distributes components, deploys PostgreSQL, initializes the database, and configures all other GDOM dependencies (GBase 8a analysis repository, Redis, RocketMQ, Nginx, etc.).
[root@vm151 GDOM-v3.7.0-build3-redhat8-x86_64]# su gdom
[gdom@vm151 GDOM-v3.7.0-build3-redhat8-x86_64]$ ./gdomInstall.sh -a
Key actions performed automatically:
- Port availability checks
- Distribution and extraction of the PostgreSQL binary
-
initdb, creation of thegdomdatabase user and database - Execution of GDOM schema and seed data SQL scripts
- Configuration and startup of all supporting services
Relevant log excerpts:
--------------------------GDOM-DB---------------------------------------
10.0.2.151 PostgreSQL extraction successful
PostgreSQL configuration successful
...
Data directory initialization successful
PostgreSQL started successfully
gdom user created successfully
gdom user privileges granted
...
Resource database gdom initialization completed
...
########################################################################
GDOM installation and deployment completed
########################################################################
2.3 Start All Services
After installation, launch all services with the provided script.
[gdom@vm151 GDOM-v3.7.0-build3-redhat8-x86_64]$ ./gdomStart.sh -a
Once started, the GDOM web console is accessible at https://10.0.2.151:8810.
3. Direct PostgreSQL Client Access
If you need to connect directly to the PostgreSQL instance, navigate to the PostgreSQL installation directory and use the included psql.sh helper.
[gdom@vm151 postgresql-17.6-redhat8-x86_64]$ ./psql.sh 10.0.2.151 5432 gdom gdom
Password for user gdom:
psql (17.6)
Type "help" for help.
gdom=#
Parameters: <host> <port> <user> <database>.
4. Summary
GDOM 3.7.0 and later fully automate the deployment of PostgreSQL as the backend resource database. This provides a viable alternative for environments that prefer PostgreSQL over MySQL. The entire process — from OS user creation and PostgreSQL initialization to schema migration and service orchestration — is handled by the installation scripts, making the setup straightforward and repeatable.
For GBase 8a administrators, this means the operational management tooling can now sit on a PostgreSQL‑backed metadata store, aligning better with site‑specific database policies without sacrificing ease of deployment.
Top comments (0)