Quick Starts

Extensions supported by ApsaraDB RDS for PostgreSQL

This topic provides an overview of the extensions and extension versions that are supported by ApsaraDB RDS for PostgreSQL instances.

Note

  • If your RDS instance does not support a few extensions that are described in the following table, you must update the minor engine version of your RDS instance to the latest version. For more information, see Update the minor engine version of an ApsaraDB RDS for PostgreSQL instance.

  • The following table describes only common extensions. If you want to query the extensions that are supported by your RDS instance, you can run the SELECT * FROM pg_available_extensions; command.

  • Before you use some extensions, you must add the names of the extensions to the value of the shared_preload_libraries parameter of your RDS instance. Otherwise, you cannot create the extensions.

    • The extensions include pg_stat_statements, auth_delay, passwordcheck, auto_explain, pg_pathman, orafce, pgaudit, pglogical, pg_bigm, pg_cron, pg_hint_plan, pg_prewarm, zhparser, timescaledb, pldebugger, sql_firewall, and pg_jieba.

    • If you want to use the pldebugger extension, you must add plugin_debugger to the value of the shared_preload_libraries parameter of your RDS instance.

    • If you want to use the sql_firewall extension and the pg_stat_statements extension at the same time, you must add sql_firewall and pg_stat_statements to the value of the shared_preload_libraries parameter. Make sure that pg_stat_statements is followed by sql_firewall.

  • For more information about how to modify the shared_preload_libraries parameter, see Manage the parameters of an ApsaraDB RDS for PostgreSQL instance.

The following tables describe the extensions that are supported by the x86 architecture and the ARM architecture. For more information about the x86 architecture and the ARM architecture, see Architectures.

Important

The extensions that are supported for ApsaraDB RDS for PostgreSQL instances are changed. Starting April 17, 2023, some extensions can no longer be created for ApsaraDB RDS for PostgreSQL instances that run minor engine versions earlier than 20230330. The existing extensions are not affected. For more information, see [Notice] Starting April 17, 2023, some extensions can no longer be created for ApsaraDB RDS for PostgreSQL instances that run earlier minor engine versions.

x86

Manage the parameters of an ApsaraDB RDS for PostgreSQL instance.

The following tables describe the extensions that are supported by the x86 architecture and the ARM architecture. For more information about the x86 architecture and the ARM architecture, see Manage the parameters of an ApsaraDB RDS for PostgreSQL instance.

The following tables describe the extensions that are supported by the x86 architecture and the ARM architecture. For more information about the x86 architecture and the ARM architecture, see Architectures.

Important

The extensions that are supported for ApsaraDB RDS for PostgreSQL instances are changed. Starting April 17, 2023, some extensions can no longer be created for ApsaraDB RDS for PostgreSQL instances that run minor engine versions earlier than 20230330. The existing extensions are not affected. For more information, see [Notice] Starting April 17, 2023, some extensions can no longer be created for ApsaraDB RDS for PostgreSQL instances that run earlier minor engine versions.

x86

Architectures.

Important

The extensions that are supported for ApsaraDB RDS for PostgreSQL instances are changed. Starting April 17, 2023, some extensions can no longer be created for ApsaraDB RDS for PostgreSQL instances that run minor engine versions earlier than 20230330. The existing extensions are not affected. For more information, see Manage the parameters of an ApsaraDB RDS for PostgreSQL instance.

The following tables describe the extensions that are supported by the x86 architecture and the ARM architecture. For more information about the x86 architecture and the ARM architecture, see Architectures.

Important

The extensions that are supported for ApsaraDB RDS for PostgreSQL instances are changed. Starting April 17, 2023, some extensions can no longer be created for ApsaraDB RDS for PostgreSQL instances that run minor engine versions earlier than 20230330. The existing extensions are not affected. For more information, see [Notice] Starting April 17, 2023, some extensions can no longer be created for ApsaraDB RDS for PostgreSQL instances that run earlier minor engine versions.

x86

[Notice] Starting April 17, 2023, some extensions can no longer be created for ApsaraDB RDS for PostgreSQL instances that run earlier minor engine versions.

x86

Extension

15

14

13

12

11

10

Description

address_standardizer

3.3.2

3.1.4

3.1.4

3.1.4

3.1.4

3.1.4

This extension is used to standardize the names of geographical locations based on Postal Address Geocoder (PAGC). For more information, see Tuning the Standardizer.

address_standardizer_data_us

3.3.2

3.1.4

3.1.4

3.1.4

3.1.4

3.1.4

This extension is used to standardize the names of the geographical locations in the United States based on PAGC. For more information, see Tuning the Standardizer.

aggs_for_arrays

Not supported

Not supported

Not supported

Not supported

Not supported

1.3.1

This extension provides an extension function that is used to compute the statistics of numeric arrays.

bloom

1.0

1.0

1.0

1.0

1.0

1.0

This extension provides an index access method that is based on Bloom filters.

btree_gin

1.3

1.3

1.3

1.3

1.3

1.2

This extension provides sample Generalized Inverted Index (GIN) operator classes that are used to implement B-tree equivalent behavior for multiple data types or all enumerated data types.

btree_gist

1.7

1.6

1.5

1.5

1.5

1.5

This extension provides sample GiST operator classes that are used to implement B-tree equivalent behavior for multiple data types or all enumerated data types.

chkpass

Not supported

Not supported

Not supported

Not supported

Not supported

1.0

This extension provides a data type that is used to store encrypted passwords.

citext

1.6

1.6

1.6

1.6

1.5

1.4

This extension provides a string type that is not case-sensitive.

cube

1.5

1.5

1.4

1.4

1.4

1.2

This extension provides a data type that is used to represent multidimensional cubes.

dblink

1.2

1.2

1.2

1.2

1.2

1.2

This extension is used to manage tables across databases.

decoderbufs

Not supported

Not supported

0.1.0

0.1.0

0.1.0

0.1.0

This extension is used to generate data that is compatible with the Debezium platform based on the Protocol Buffers protocol.

dict_int

1.0

1.0

1.0

1.0

1.0

1.0

This extension provides a sample add-on dictionary template that is used to run full-text searches.

earthdistance

1.1

1.1

1.1

1.1

1.1

1.1

This extension provides two different methods that are used to compute great-circle distances on the surface of the Earth.

encdb

1.1.12

1.1.12

1.1.12

1.1.12

1.1.12

1.1.12

This extension is used to support fully encrypted databases.

fuzzystrmatch

1.1

1.1

1.1

1.1

1.1

1.1

This extension is used to compute the similarity and distance between strings.

ganos_address_standardizer

5.4

5.4

5.4

5.4

5.3

5.3

This extension is used to standardize the names of geographical locations based on PAGC. For more information, see Tuning the Standardizer.

ganos_address_standardizer_data_us

5.4

5.4

5.4

5.4

5.3

5.3

This extension is used to standardize the names of the geographical locations in the United States based on PAGC. For more information, see Tuning the Standardizer.

ganos_geometry

5.4

5.4

5.4

5.4

5.3

5.3

This extension is used to compute and analyze spatial geometries.

ganos_geometry_pyramid

5.4

5.4

5.4

5.4

5.3

5.3

This extension is used to display 2D geometric big data at high speeds.

ganos_geometry_pyramid

5.4

5.4

5.4

5.4

5.3

5.3

This extension is used to display 2D geometric big data at high speeds.

ganos_geometry_pyramid

5.4

5.4

5.4

5.4

5.3

5.3

This extension is used to display 2D geometric big data at high speeds.

ganos_geometry_sfcgal

5.4

5.4

5.4

5.4

5.3

5.3

This extension is an extension of the SFCGAL extension and is used to process spatial geometries.

ganos_geometry_topology

5.4

5.4

5.4

5.4

5.3

Was this helpful?

open

Related Resources

Database
Development and O&M recommendations for ApsaraDB RDS for PostgreSQL
The article provides development and operation recommendations for Alibaba Cloud ApsaraDB for RDS for PostgreSQL. It covers topics such as database design, performance optimization, security management, backup and recovery, and disaster recovery. The article also includes best practices and guidelines for database development and operation. It also explains the features and benefits of ApsaraDB for RDS for PostgreSQL, and how it can help in improving database performance, scalability, and availability.
Database
Scenarios of ApsaraDB RDS
The article provides an overview of various scenarios where Alibaba Cloud ApsaraDB for RDS can be used for database management. It covers scenarios such as e-commerce applications, gaming applications, financial applications, and big data applications. The article explains how ApsaraDB for RDS can help in improving database performance, scalability, and availability. It also includes use cases and best practices for each scenario.
Database
Competitive advantages of ApsaraDB RDS instances over self-managed databases
ApsaraDB RDS provides highly available, reliable, secure, and scalable managed databases that are comparable to commercial databases in terms of performance. The managed databases cost less than self-managed databases that are deployed on Elastic Compute Service (ECS) instances and third-party database servers. This reduces the deployment and maintenance costs.
Database
Use ApsaraDB RDS with self-managed database instances for geo-disaster recovery
The article explains how to use ApsaraDB for RDS in conjunction with self-managed database instances for geo-disaster recovery on the Alibaba Cloud platform. It describes how self-managed database instances can be used to store and manage data in different geographical locations, and how ApsaraDB for RDS can be used to replicate and synchronize data between the instances. The article provides step-by-step instructions for configuring and managing cross-region replication between ApsaraDB for RDS and self-managed database instances using various methods such as snapshot synchronization and binlog replication. Additionally, the article explains the benefits of using ApsaraDB for RDS with self-managed database instances for geo-disaster recovery, such as improved data availability, disaster recovery, and business continuity. The article is intended for users who want to understand how to leverage the capabilities of ApsaraDB for RDS and self-managed database instances to ensure the availability and reliability of their data in the event of a disaster.