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 6.
Specifications
Resource Type |
Specifications |
Description |
---|---|---|
Storage space |
|
To increase the upper limit of the storage space to 10 TB when cloud SSDs or extreme SSDs are used, contact customer service. |
Connections |
The minimum number is 10 and the theoretical maximum number is 262,143. The actual maximum value dynamically changes. |
The maximum number of connections supported depends on memory specifications. For details, see Configuration of Maximum Connections. |
IOPS |
|
The input/output operations per second (IOPS) supported depends on the I/O performance of Elastic Volume Service (EVS) disks. For details, see the description about ultra-high I/O and extreme SSDs in Disk Types and Performance of Elastic Volume Service Service Overview. |
Quotas
Resource Type |
Constraint |
Description |
---|---|---|
Tags |
Each instance can have up to 20 tags. |
For more information, see Tags. |
Free backup space |
GaussDB provides free backup space of the same size as your purchased storage space. |
After you pay for the storage space of your instance, you will get a backup space of the same size for free. For more information, see How Is GaussDB Backup Data Billed? |
Retention period of automated backups |
The default value is 7 days. The value ranges from 1 to 732 days. |
For more information, see Configuring an Automated Backup Policy for Instances. |
Naming
Item |
Description |
---|---|
Instance name |
|
Backup name |
|
Parameter template name |
|
Security
Item |
Description |
---|---|
root permissions |
Only the root user permissions are available on the instance creation page.
NOTE:
After August 30, 2022, the root user of newly created instances and upgraded existing instances has the sysadmin permission. To upgrade your existing instance, contact technical support. If your existing instances are not upgraded, the root user only has the following permissions: createrole, createdb, and monadmin. The root user has fewer permissions than the administrator. When some SQL syntax or functions, such as CREATE TABLESPACE, are executed, an error message is displayed, indicating that the permissions are insufficient. |
root password |
For more information, see Resetting the Administrator Password. |
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. For more information, see Changing the Database Port. |
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 |
|
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.
|
Instance Operations
Function |
Constraints |
---|---|
Database access |
|
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 |
|
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 |
|
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 |
Restoring data to an existing instance |
No |
Yes |
Scaling up storage |
Yes |
Yes |
Changing instance specifications |
Yes |
Yes |
Hot patch installation |
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 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot