Help Center/ GaussDB/ Service Overview/ Notes and Constraints
Updated on 2025-08-18 GMT+08:00

Notes and Constraints

To ensure the stability and security of GaussDB, certain constraints are put in place for access or permissions control.

There is no SLA commitment, so GaussDB single-replica instances cannot be used in production environments. For function constraints of single-replicas, see Table 4.

Naming

Table 1 Naming constraints

Item

Description

Instance name

  • 4 to 64 characters long
  • Must start with a letter (case-sensitive). Only letters, digits, hyphens (-), and underscores (_) are allowed.

Backup name

  • 4 to 64 characters long
  • Must start with a letter (case-sensitive). Only letters, digits, hyphens (-), and underscores (_) are allowed.

Parameter template name

  • 1 to 64 characters long
  • Only letters (case-sensitive), digits, hyphens (-), underscores (_), and periods (.) are allowed.

Security

Table 2 Security constraints

Item

Description

root permissions

Only the root user permissions are available on the instance creation page.

root password

  • 8 to 32 characters long
  • Must contain at least three types of the following: uppercase letters, lowercase letters, digits, and special characters. Supported characters: ~!@#%^*-_=+?,

For more information, see .

Database port

The port ranges from 1024 to 39989, but the following ports that are reserved for system use cannot be used: 2378 to 2380, 2400, 4999 to 5001, 5100, 5500, 5999 to 6001, 6009 to 6010, 6500, 8015, 8097, 8098, 8181, 9090, 9100, 9180, 9187, 9200, 12016, 12017, 20049, 20050, 21731, 21732, 32122 to 32126, and 39001.

Disk encryption

If you enable disk encryption during instance creation, the disk encryption status and the key cannot be changed later.

VPC

The VPC where a GaussDB instance is located cannot be changed after the instance is created.

Security group

  • By default, each tenant can create up to 500 security group rules.
  • It is recommended that a security group contain a maximum of 50 rules.

System accounts

To provide O&M services, the system automatically creates system accounts when you create GaussDB instances. These accounts cannot be used by users.

  • rdsAdmin: a management account with the highest permission.
  • rdsBackup: a backup account. It is used for backend backup.
  • rdsRepl: an account used to synchronize data from the primary instance to the standby instance.
  • root: the system administrator account.
  • rdsMetric: a metric monitoring account. It is used to obtain GaussDB performance metrics and report them to Cloud Eye for the tenant to view the status of GaussDB.

Instance Operations

Table 3 Constraints on instance operations

Function

Constraints

Database access

  • The ECSs must be allowed by the security group to access the target GaussDB instance.

    If a GaussDB instance and the ECSs belong to different security groups, no communication between them is established by default. To allow it, you must add an inbound rule to the GaussDB security group.

  • The default port number of GaussDB instances is 8000.

Deployment

The servers where instances are deployed are not directly visible to you. You can only access the instances through IP addresses and database ports.

Rebooting a GaussDB instance

GaussDB instances cannot be rebooted through commands. They must be rebooted on the management console.

Querying GaussDB backups

GaussDB backup files are stored in OBS buckets and are not visible to you.

Specification changes

  • Before you change the instance specifications, ensure that the instance is available. If the instance or node is abnormal, or the storage space is full, you cannot perform this operation.
  • During the specification change for HA (1 primary + 2 standby) instances, a primary/standby failover is triggered. During the failover, services are interrupted for about 1 minute.
  • For a single-replica instance, changing instance specifications will reboot the instance and interrupt services for 5 to 10 minutes.
  • Changing the CPU and memory specifications will cause the instance to reboot, and services will be temporarily interrupted during the reboot.

Failover

For centralized instances, services are unavailable for about 10 seconds when the primary node is being switched to the standby node.

Data restoration

To prevent data loss, you are advised to back up key data before data restoration.

Storage space

If the storage space of an instance is full, data cannot be written to databases. You are advised to periodically check the storage space.

Performance tuning

Performance tuning may need to reboot the instance and interrupt services.

Recycle bin management

  • GaussDB allows you to move unsubscribed yearly/monthly instances and deleted pay-per-use instances to the recycle bin. You can restore an instance that was deleted up to 7 days ago from the recycle bin.
  • The recycle bin is enabled by default and cannot be disabled. The deleted instances can be retained for 7 days by default.
Table 4 Function constraints of single-replica centralized instances

Function

Supported by Versions Earlier Than V2.0-3.0

Supported by V2.0-3.0 and Later

Creating an instance

Yes

Yes

Rebooting an instance

Yes

Yes

Modifying parameters

Yes

Yes

Applying parameters

Yes

Yes

Resetting a password

Yes

Yes

Creating a full backup

No

Yes

Creating a differential backup

No

Yes

Deleting a backup

No

Yes

Modifying the backup policy

No

Yes

Restoring data to the original instance

No

Yes

Restoring data to a new instance

No

Yes

Scaling up storage

Yes

Yes

Changing instance specifications

Yes

Yes

Hot patch update

No

Yes

In-place upgrade

Yes (The version can be upgraded only to V2.0-3.0 or later.)

Yes

Gray upgrade

No

Yes (only supported in version V2.0-3.207 or later)

Viewing monitoring metrics

Yes

Yes

Deleting an instance

Yes

Yes

Rebuilding a deleted instance from the recycle bin

No

Yes

Querying the disk usage

Yes

Yes

Creating a database

Yes

Yes

Querying a database

Yes

Yes

Creating a schema and user

Yes

Yes

Deleting a schema and user

Yes

Yes

Performing database operations

Yes

Yes