This topic describes the release notes for the minor versions, console, Ganos, and API of PolarDB for PostgreSQL and provides links to the relevant references.
You can execute the following statement to view the database engine revision version of your PolarDB for PostgreSQL cluster:
SHOW polardb_version;The database engine revision version numbers of PolarDB for PostgreSQL clusters have been changed to a 6-digit format starting from February 26, 2025 (UTC+8). For more information of this change, including the mapping between the old and new version numbers, see Revision version numbers of PolarDB for PostgreSQ clusters changed to a 6-digit format.
The following table describes the version mappings between PolarDB for PostgreSQL and open source PostgreSQL.
PolarDB for PostgreSQL version | Open source PostgreSQL version |
V1.1.7 | 11.9 |
V1.1.6 | 11.9 |
V1.1.5 | 11.8.15 |
V1.1.4 | 11.5.12 |
V1.1.3 | 11.5.12 |
V1.1.2 | 11.2 |
V1.1.1 | 11.2c |
V1.1.0 | 11.2 |
1.1.7
Minor version
Category | Feature | Description | References | Release date |
New feature | Compatibility | This minor version is compatible with PostgreSQL 11.9.20. | N/A | December 2020 |
Optimized feature | Maximum number of connections | The maximum number of connections is adjusted for some compute node specifications. | Compute node specifications of PolarDB for PostgreSQL Enterprise Edition | December 2020 |
Ganos V3.2
Category | Feature | Description | References | Release date |
New feature | ST_AsPNG | BYTEA-type images can be returned for vector pyramids. This feature can be used to visualize vector data. | December 2020 | |
Raster data | The JPEG 2000 compression algorithm is added. This algorithm is used to compress 16-bit raster data before the data is stored. | N/A | December 2020 | |
Optimized feature | st_dwithin | The ST_DWithin function is optimized to query distances at higher performance. | N/A | December 2020 |
Fixed issue | The bug that causes an improper intersection of trajectory objects on the t axis is fixed. | December 2020 | ||
The issues related to the memory topology indexes that are supported by Ganos are fixed. | December 2020 | |||
1.1.6
Minor version
Category | Feature | Description | References | Release date |
New feature | Compatibility | This minor version is compatible with PostgreSQL 11.9. | N/A | November 2020 |
Primary/secondary switchover | By default, the OnlinePromote feature is enabled. This feature reduces the amount of time that is consumed by a failover and improves cluster availability. | November 2020 | ||
Fixed issue | The following issue is fixed: A node does not restart smoothly in some scenarios. | November 2020 | ||
The following issue is fixed: In some scenarios, instances do not respond due to OOM errors. | November 2020 | |||
The following issue is fixed: In some scenarios, read-only nodes do not respond. | November 2020 | |||
V3.1
Ganos V3.1
Category | Feature | Description | References | Release date |
New feature | Trajectory data type | GiST indexes are supported for trajectory objects, and six operator families are provided for users to create GiST indexes in six dimensions. | N/A | October 2020 |
The BOXND data type is added. This data type is used to describe the spatio-temporal extents of trajectory objects and store trajectory objects. | N/A | October 2020 | ||
The following operators are supported: the && operator, the @> operator, and the <@ operator. These operators are used to compare the spatio-temporal relationships between two specified objects from various dimensions. The && operator is used to check whether the two specified objects intersect. The @> operator is used to check whether the left operand-specified object includes the right operand-specified object. The <@ operator is used to check whether the left operand-specified object is included in the right operand-specified object. | N/A | October 2020 | ||
The ST_ndIntersects, ST_ndDWithin, ST_ndContains, and ST_ndWithin functions are supported to process trajectories. | October 2020 | |||
New features are added. These features are used to collect statistics about trajectory objects and estimate scan costs based on the statistics. | N/A | October 2020 | ||
TrajGiST indexes are supported. TrajGiST indexing is an improved indexing method. | N/A | October 2020 | ||
ganos_update function | The ganos_update function is added. Users can run the | N/A | October 2020 | |
Optimized feature | Spatio-temporal range query | Spatio-temporal range queries are optimized. The query performance is improved by using optimized GiST index-based two-phase queries. | N/A | October 2020 |
Vector pyramid | Source data from all the coordinate systems that provide spatial reference identifiers (SRIDs) is supported. The source data can be tiles that are based on the EPSG:3857 or EPSG:4326 coordinate reference system. | N/A | October 2020 | |
The pixelSize parameter is supported. This parameter is used to aggregate point data and reduce the number of tiles. | N/A | October 2020 | ||
Fixed issue | The bug that causes failures in updating rasters is fixed. | October 2020 | ||
The following issue is fixed: An unexpected exit may occur after the binary files of Ganos are upgraded to later versions. | October 2020 | |||
The bug that causes an abnormally large number of tiles at the top layer of a vector pyramid when the default parameter settings are used to build point data for the vector pyramid is fixed. | October 2020 | |||
1.1.4
Minor version
Category | Feature | Description | References | Release date |
New feature | ali_decoding plug-in | The ali_decoding plug-in is supported. This plug-in is used to synchronize incremental DML statements between databases. | N/A | September 2020 |
Views | The views that display process status statistics are added. | N/A | September 2020 | |
The views that display time consumption statistics for SQL statements are added. | N/A | September 2020 | ||
Audit logging | SQL errors are recorded in audit logs. | N/A | September 2020 | |
Fixed issue | The following issue is fixed: In specific scenarios, page prefetching may cause deadlocks. | September 2020 | ||
The following issue is fixed: A JOIN query fails to retrieve the accurate partition during partition pruning. | September 2020 | |||
Ganos V3.0
Category | Feature | Description | References | Release date |
New feature | Support for the subset raster in a NetCDF raster file that has multiple subsets | Network Common Data Form (NetCDF) files that contain subsets are supported. These files can be imported into specified layers based on the layer names that users specify. | N/A | September 2020 |
Custom metadata and time series information of rasters | The ST_MetaItems function is supported. This function is used to obtain the names of all custom metadata items. | September 2020 | ||
The ST_MetaData function is supported. This function is used to obtain custom metadata items of a raster and return custom metadata items in the JSON format. | September 2020 | |||
The ST_SetMetaData function is supported. This function is used to specify a metadata item. | September 2020 | |||
The ST_BeginDateTime function is supported. This function is used to obtain the start time of a raster. | September 2020 | |||
The ST_EndDateTime function is supported. This function is used to obtain the end time of a raster. | September 2020 | |||
The ST_SetBeginDateTime function is supported. This function is used to configure the start time of a raster. | September 2020 | |||
The ST_SetEndDateTime function is supported. This function is used to configure the end time of a raster. | September 2020 | |||
The ST_SetDateTime function is supported. This function is used to configure the start time and end time of a raster and the time when a band is obtained. | September 2020 | |||
Support for converting a raster into a BYTEA-type image | The ST_AsImage function is supported. This function is used to convert a raster into a BYTEA-type image. | September 2020 | ||
The ST_AsPng function is supported. This function is used to convert a raster into a BYTEA-type PNG image. | September 2020 | |||
The ST_AsJPEG function is supported. This function is used to convert a raster into a BYTEA-type JPEG image. | September 2020 | |||
Support for the GeomGrid data type and operations | The GeomGrid data type is supported. | September 2020 | ||
The ST_AsText function is supported. This function is used to convert a grid into a text representation. | September 2020 | |||
The ST_AsGeometry function is supported. This function is used to obtain the geometric representation of a grid. | September 2020 | |||
The ST_AsBinary function is supported. This function is used to convert a grid into a binary representation. | September 2020 | |||
The ST_AsBox function is supported. This function is used to obtain the box representation of a grid. | September 2020 | |||
The ST_AsGrid function is supported. This function is used to query the grids that intersect with a geometric object. | September 2020 | |||
The ST_GridFromText function is supported. This function is used to convert a grid from a text representation into a GeomGrid representation. | September 2020 | |||
The ST_GridFromBinary function is supported. This function is used to convert a grid from a binary representation into a GeomGrid representation. | September 2020 | |||
The ST_Intersects function is supported. This function is used to identify the spatial relationship between two raster objects or between a raster object and a geometric object. This function allows you to check whether the first specified object intersects with the second specified object. | September 2020 | |||
The ST_Contains function is supported. This function is used to identify the spatial relationship between two raster objects or between a raster object and a geometric object. This function allows you to check whether the first specified object contains the second specified object. | September 2020 | |||
The ST_Within function is supported. This function is used to identify the spatial relationship between two grid objects or between a grid object and a geometric object. This function allows you to check whether the first specified object is within the second specified object. | September 2020 | |||
Rapid display and storage of vector data | The ST_BuildPyramid function is supported. This function is used to create a vector pyramid. | September 2020 | ||
The ST_DeletePyramid function is supported. This function is used to delete a vector pyramid. | September 2020 | |||
The ST_Tile function is supported. This function is used to obtain vector data in the MVT format. | September 2020 | |||
Fixed issue | The following issue is fixed: In some cases, OOM errors occur when you create pyramids. | September 2020 | ||
The following issue is fixed: Trajectory objects on January 1, 2000 cannot be created. | September 2020 | |||
The bug due to which the ST_Intersection function returns inaccurate sub-trajectories for a moving object is fixed. | September 2020 | |||
The following issue is fixed: The system stops responding during a Ganos upgrade. | September 2020 | |||
This minor version is compatible with PostGIS 2.5.4. | September 2020 | |||
1.1.3
Minor version
Category | Feature | Description | References | Release date |
New feature | Views | The views that display SQL execution statistics are added. | N/A | August 2020 |
The views that display queries per second (QPS) statistics are added. | N/A | August 2020 | ||
The views that display CGroup status statistics are added. | N/A | August 2020 | ||
Fixed issue | The following issue is fixed: An error occurs when the Segmented Least Recently Used (SLRU) algorithm is used to calculate the memory size. | August 2020 | ||
The following issue is fixed: Read-only nodes are recreated due to a playback latency. | August 2020 | |||
Ganos V2.9
Category | Feature | Description | References | Release date |
New feature | Support for Cloud Optimized GeoTIFF (COG) files | The COG files are supported. The pyramid information that is stored in COG files can be read. | N/A | August 2020 |
ST_AddZ function | The ST_AddZ function is supported. This function is used to specify the Z coordinate of a geometry object based on the pixel value of the raster that is converted from the geometry object. | August 2020 | ||
Enhanced capabilities for obtaining the spatial extent information about raster objects | The ST_Extent function is supported. This function is used to retrieve the spatial extent of a raster object and return the box representation of the raster object. | August 2020 | ||
The ST_Envelope function is supported. This function is used to retrieve the spatial extent of a raster object and return the spatial extent in the format of a geometry object. | August 2020 | |||
The ST_ConvexHull function is supported. This function is used to retrieve the spatial extent of a raster object and return the spatial extent in the format of a geometry object. | August 2020 | |||
The ST_Height function is supported. This function is used to retrieve the pixel height of a raster object. | August 2020 | |||
The ST_Width function is supported. This function is used to retrieve the pixel width of a raster object. | August 2020 | |||
Fixed issue | The following issue is fixed: Performance bottlenecks occur when raster objects that are stored in external storage locations use a chunking dimension of 1 × n. You can configure storage parameters to customize the size of the chunking dimension. | August 2020 | ||
The bug due to which the ST_Values function returns linear objects whose coordinates on specific axes do not follow the sorting rules is fixed. | August 2020 | |||
The bug due to which the ST_BestPyramidLevel function returns negative values is fixed | August 2020 | |||
The bug due to which the ST_BuildPyramid function repeatedly builds pyramids is fixed. | August 2020 | |||
The bug due to which chunk tables cannot be cleared in a timely manner when you truncate raster tables is fixed. | August 2020 | |||
The bug due to which the ST_ExportTo function is invalid on the CreateOption parameter is fixed. | August 2020 | |||
The bug that causes errors when the ST_ClearChunks function is invoked is fixed. This bug is triggered when the name of the table on which the function is invoked contains both uppercase letters and lowercase letters. | August 2020 | |||
The bug that causes failures in creating an overview for an external pyramid is fixed. | August 2020 | |||
The bug that causes failures in creating an internal pyramid for a raster that has an external pyramid is fixed. | August 2020 | |||
The bug due to which inaccurate statistics are returned for queries on rasters is fixed. This bug is triggered when the rasters contain NaN values. | August 2020 | |||
1.1.2
Minor version
Category | Feature | Description | References | Release date |
New feature | Temporary table | Temporary tables can be written to local storage. This improves the read and write performance of temporary tables. | N/A | July 2020 |
Event trigger | Logical replication can be performed on events captured by the event trigger. Accounts that have the polar_superuser permissions can perform logical replication. | N/A | July 2020 | |
Custom resource group | Requests can be initiated by custom resource groups. | N/A | July 2020 | |
Optimized feature | Process of recovery from a failure | The process to recover from a failure is optimized. This reduces the amount of time that is required to recover from a failure in extreme cases. | N/A | July 2020 |
Fixed issue | The following issue is fixed: Accounts that have the polar_superuser permissions cannot use the Index Advisor. | July 2020 | ||
Ganos V2.8
Category | Feature | Description | References | Release date |
New feature | Enhanced interfaces that are used to access raster metadata | The ST_XMin function is supported. This function is used to obtain the minimum value in a set of rasters on the X-axis. | July 2020 | |
The ST_YMin function is supported. This function is used to obtain the minimum value in a set of rasters on the Y-axis. | July 2020 | |||
The ST_XMax function is supported. This function is used to obtain the maximum value in a set of rasters on the X-axis. | July 2020 | |||
The ST_YMax function is supported. This function is used to obtain the maximum value in a set of rasters on the Y-axis. | July 2020 | |||
The ST_ChunkHeight function is supported. This function is used to obtain the height of a raster tile. | July 2020 | |||
The ST_ChunkWidth function is supported. This function is used to obtain the width of a raster tile. | July 2020 | |||
The ST_ChunkBands function is supported. This function is used to obtain the number of bands of a raster tile. | July 2020 | |||
ST_SrFromEsriWkt function | The ST_SrFromEsriWkt function is supported. This function is used to convert the format of a spatial reference string from Esri into Open Geospatial Consortium (OGC). | July 2020 | ||
Raster data type | The Zstandard (Zstd) compression algorithm and the Snappy compression algorithm are added. These algorithms are used to compress raster data. | N/A | July 2020 | |
Point cloud data type | Point cloud files can be copied in binary format. | N/A | July 2020 | |
Environment variables | The PROJ_LIB and GDAL_DATA environment variables can be configured, and the relevant data can be deployed. | N/A | July 2020 | |
Fixed issue | The bug due to which Ganos unexpectedly exits when an invalid OSS path is specified is fixed. | July 2020 | ||
The bug that causes inconsistencies between the imported SRIDs and original SRIDs of specific rasters is fixed. | July 2020 | |||
1.1.1
Minor version
Category | Feature | Description | References | Release date |
New feature | polar_proxy_utils plug-in | The polar_proxy_utils plug-in is supported. This plug-in is used to manage proxy-related features. This plug-in allows you to configure read-only Universal Disk Format (UDF) files and read-only tables. This plug-in also allows you to use a cluster endpoint to route requests for accessing read-only UDF files and read-only tables to the read-only nodes in the cluster. | N/A | June 2020 |
polar_resource_group plug-in | The polar_resource_group plug-in is supported. This plug-in is used to customize resource groups. You can use the custom resource groups to isolate resources such as CPUs and memory on a per-user, per-database, or per-session basis. | N/A | June 2020 | |
Optimized feature | Reliability and availability | The compute nodes of databases are decoupled from file systems. This allows you to perform O&M operations on the file systems. This improves the reliability and availability of databases. | N/A | June 2020 |
Transaction processing | The snapshot of the active transaction list is replaced with a commit sequence number (CSN). Each CSN is a monotonically increasing identifier. This improves the transaction processing performance of databases. | N/A | June 2020 | |
Execution plan | Execution plans are optimized to prevent obsolete statistics from being used. | N/A | June 2020 | |
Fixed issue | The following issue is fixed: A database process failure occurs when the timescaledb plug-in fails to request memory resources. | June 2020 | ||
The following issue is fixed: The I/O monitoring feature does not provide data statistics after a process exits. | June 2020 | |||
The following issue is fixed: A null pointer exception may occur after lock_debug is enabled. | June 2020 | |||
The following issue is fixed: In specific cases, the pg_cron plug-in becomes unavailable. | June 2020 | |||
Known issues of distributed shared memory (DSM) deadlocks in the community edition are fixed. | June 2020 | |||
The following issue is fixed: The number of connections exceeds the upper limit. | June 2020 | |||
1.1.0
Minor version
Category | Feature | Description | References | Release date |
New feature | polar_concurrency_control plug-in | The polar_concurrency_control plug-in is supported. This plug-in is used to configure a concurrency limit on transaction executions, SQL queries, stored procedures, and DML operations. You can customize large queries and configure a concurrency limit on large queries to improve the execution efficiency in high concurrency scenarios. | N/A | May 2020 |
oss_fdw plug-in | The oss_fdw plug-in is supported. This plug-in is used to support external tables of Alibaba Cloud OSS. You can use OSS external tables to write data of databases to OSS or load data from OSS to databases. You can use multiple external tables in parallel or compress data during imports and exports. This improves the performance of data imports and exports. You can also use this feature to separate hot data and cold data that are stored in a wide range of storage media. | May 2020 | ||
Optimized feature | polar_stat_activity view | The polar_stat_activity view is optimized. The wait_info and wait_time columns are added. The wait_info column displays the object for which the current process is waiting. The wait_time column displays the amount of time for which the process needs to wait. If the object is a process, the process identifier (PID) is displayed. If the object is a file, the file descriptor (FD) is displayed. | N/A | May 2020 |
Indexing | The pre-extension feature is supported. This feature automatically adds additional index pages when index pages are insufficient for new indexes. This improves the execution performance when data is inserted into a table that has indexes. | N/A | May 2020 |
Ganos V2.7
Category | Feature | Description | References | Release date |
New feature | MD5 functions | The ST_MD5Sum function is supported. This function is used to obtain the MD5 hash value of a raster object. | May 2020 | |
The ST_SetMD5Sum function is supported. This function is used to configure the MD5 hash value of a raster object. | May 2020 | |||
Authentication method of spatial raster objects that are stored in OSS | The ST_AKId function is supported. This function is used to obtain the AccessKey ID that is used to access a raster object stored in OSS. | May 2020 | ||
The ST_SetAccessKey function is supported. This function is used to configure the AccessKey ID and the AccessKey secret that are used to access a raster object stored in OSS. | May 2020 | |||
The ST_SetAKId function is supported. This function is used to configure the AccessKey ID that is used to access a raster object stored in OSS. | May 2020 | |||
The ST_SetAKSecret function is supported. This function is used to configure the AccessKey secret that is used to access a raster object stored in OSS. | May 2020 | |||
Functions that are used to manage spatial raster metadata | The ST_ScaleX function is supported. This function is used to obtain the pixel width of a raster object on the X-axis of the spatial reference system. | May 2020 | ||
The ST_ScaleY function is supported. This function is used to obtain the pixel width of a raster object on the Y-axis of the spatial reference system. | May 2020 | |||
The ST_SetScale function is supported. This function is used to configure the pixel width of a raster object in the spatial reference system. | May 2020 | |||
The ST_SkewX function is supported. This function is used to obtain the skew of a raster object on the X-axis of the spatial reference system. | May 2020 | |||
The ST_SkewY function is supported. This function is used to obtain the skew of a raster object on the Y-axis of the spatial reference system. | May 2020 | |||
The ST_SetSkew function is supported. This function is used to specify the skew of a raster object in the spatial reference system. | May 2020 | |||
The ST_UpperLeftX function is supported. This function is used to obtain the upper-left X-coordinate of a raster object in the spatial reference system. | May 2020 | |||
The ST_UpperLeftY function is supported. This function is used to obtain the upper-left Y-coordinate of a raster object in the spatial reference system. | May 2020 | |||
The ST_SetUpperLeft function is supported. This function is used to configure the upper-left coordinates of a raster object in the spatial reference system. | May 2020 | |||
The ST_PixelWidth function is supported. This function is used to obtain the pixel width of a raster object in the spatial reference system. | May 2020 | |||
The ST_PixelHeight function is supported. This function is used to obtain the pixel height of a raster object in the spatial reference system. | May 2020 | |||
Fixed issue | The following issue is fixed: Aggregate functions result in extension upgrade failures. | May 2020 | ||