To ensure the stability and security of instances, AnalyticDB for PostgreSQL is subject to the following limits.
You do not need to perform basic database O&M operations such as ensuring high availability and installing security patches for purchased AnalyticDB for PostgreSQL instances. However, you must take note of the following items:
- Instance upgrade: Instances are read-only while they are being upgraded. A service interruption of up to 30 seconds may occur after the upgrade is complete. Make sure that your application is configured with automatic reconnection policies such as a connection pool.
- Failover: The coordinator and compute nodes each adopts a primary/secondary high-availability architecture. When an error occurs on the primary node, the service is automatically switched over to the secondary node within 30 seconds. A service interruption of about 30 seconds may occur during the failover. Make sure that your application is configured with automatic reconnection policies such as a connection pool.
|Maximum number of user connections||The maximum number of connections varies with the instance specifications:
|Maximum data volume in a column||1 GB|
|Maximum data volume of a database||The maximum data volume of a database varies with the instance specifications.|
|Maximum data volume of a table||128 TB per partition|
|Maximum volume of BLOB data||1 GB
Note In AnalyticDB for PostgreSQL, the BYTEA data type is used in place of BLOB.
|Maximum number of rows in a table||2^48|
|Maximum number of columns in a table||1,600|
|Maximum number of tables in a database||4.2 billion|
|Maximum number of columns in a view||1,664|
|Maximum number of characters in the name of a row, table, or database||128|
|Maximum number of characters in the name of an object (database, user, base table, view, index, stored procedure, UDF, UDT, constraint, or column)||63|
|Maximum number of columns in a primary or secondary index||32|
|Maximum number of columns specified in a SELECT statement||1,664|