Content

Target customers: all AnalyticDB for PostgreSQL users. Features released: New features: AnalyticDB for PostgreSQL now supports multiple coordinator nodes. The number of connections and the I/O performance linearly increase with the number of coordinator nodes based on the scalability of compute nodes. AnalyticDB for PostgreSQL also supports point-in-time recovery (PITR), two or more compute nodes for data synchronization, change of instance resource type from reserved mode to elastic mode, and time formats in AnalyticDB for MySQL V2.0 such as 2020-08-03T23:59:59. Indexes for JSON fields can be created, deleted, or disabled by executing ALTER TABLE statements. The BINARY type is supported for the metadata of the protocol layer. File headers can be exported when you export data from AnalyticDB for PostgreSQL to a single Object Storage Service (OSS) object by using an external table. If the number of exported rows exceeds the maximum number, extra rows are exported to one or more new objects. You can specify both the maximum size and maximum number of rows in an object. Extra objects are created based on the limit that is reached earlier. Execution plans of slow SQL queries can be viewed in the AnalyticDB for PostgreSQL console. The INSERT INTO SELECT ON DUPLICATE KEY UPDATE query is supported when the input values in the UPDATE column are constants or when the input values in the UPDATE column are those in the SELECT column. The ORC format is supported for OSS foreign tables. The priority of BATCH LOAD statements can be specified by using hints. Optimized features: Performance is improved when the pushdown logic of LIMIT n statements is used to filter data. The BOOL and BOOLEAN types are supported for table creation statements. Database names can start with an uppercase letter or an underscore (_). Fixed issues: The issue that may cause index exceptions when indexes are added or removed at the same time is fixed. The issue that may cause java.lang.NullPointerException errors when data is inserted to a table that does not exist is fixed. The issue that may cause data query failures if partition fields exist in Parquet-formatted files when OSS partition tables are pushed down is fixed. The issue that may cause Premature end of Content-Length errors when you access OSS is fixed. The issue that may cause com.alibaba.fastsql.sql.ast.expr.SQLMethodInvokeExpr cannot be cast to com.alibaba.fastsql.sql.ast.SQLName errors when ADD KEY statements are executed is fixed. The issue that may cause "no composite key to add" errors due to composite keys when tables are managed in hot or cold storage is fixed.