Amazon RDS for PostgreSQL updates

• Fixed a bug allowing the querying of the security invoker views as an unprivileged user.

• Fixed a bug preventing tds_fdw from connecting when TLS is enabled.

• Fixed a bug preventing upgrades to PostGIS version 3.4.1.

• Fixed an error with the aws_s3 extension when the Region was not provided.

• The pg_partman extension was updated to 5.0.1.

• The pg_tle extension was updated to 1.4.0.

• The pgactive extension was updated to 2.1.3.

• The pgtap extension was updated to 1.3.2.

• The pgvector extension was updated to 0.6.2.

New features and enhancements

• Added support for pg_log_standby_snapshot

• Fixed the multisecond latency on the aws_lambda calls

• Fixed a bug preventing the termination of autovacuum

• Fixed a bug preventing the creation of the h3 extension

This version includes the following changes:

• The orafce extension was updated to version 4.9.0.

• The pg_repack extension was updated to version 1.5.0.

• The pgactive extension was updated to version 2.1.2.

• The pgvector extension was updated to 0.6.0.

• The plv8 extension was updated to 3.1.10.

• The PostGIS extension was updated to 3.4.1.

New features and enhancements

• Fixed a crash in CatalogCacheComputeHashValue with dblink_connect due to a Null or invalid connection

• Supported the Amazon SDK version of the aws_s3 extension

• Blocked the meta-command execution, for example, \copy, \i, and \lo_export in psql

• Fixed the overflow in the pg_transport extension

• Removed the unsupported shared libraries from the engine binary

This version includes the following changes:

• The plrust extension was updated to version 1.2.7.

• The plv8 extension was updated to version 3.1.9.

New features and enhancements

• The aws-lc now uses a FIPS version.

• Allow setting TLS 1.3 as the ssl_min_protocol_version and ssl_max_protocol_version.

• The pgactive extension was added.

• The pglogical extension was added.

• By default, the default_toast_compression DB instance parameter is set to lz4.

• The rds.rds_superuser_reserved_connections parameter has been deprecated in RDS for PostgreSQL version 16. The reserved_connections parameter should be utilized to reserve the number of connection slots. The reserved_connections parameter sets the number of connection slots reserved for roles with the pg_use_reserved_connections privileges. rds_superuser is a member of the pg_use_reserved_connections role by default. For more information, see the PostgreSQL documentation reserved connections.

This version includes the following changes:

• The hll extension was updated to version 2.1.8.

• The oracle_fdw extension was updated to version 2.6.0.

• The orafce extension was updated to version 4.6.1.

• The pg_cron extension was updated to version 1.6.1.

• The pg_partman extension was updated to version 5.0.0.

• The pgtap extension was updated to version 1.3.1.

• The pgvector extension was updated to version 0.5.1.

• The plprofiler extension was updated to version 4.2.4.

• The plrust extension was updated to version 1.2.6.

• The plv8 extension was updated to version 3.1.8.

• The rdkit extension was updated to version 4.4.0.

This version includes the following changes:

• The mysql_fdw extension was updated to version 2.9.1

• The pgrouting extension was updated to version 3.5.0

• The pgvector extension was updated to version 0.5.0

New extensions

• The pg_proctab extension was added.

• The rdkit extension was added.

• The hll extension was added.

• The pg_cron extension was added.

This version also includes the following change:

• The PostGIS extension was updated to version 3.4.0.

New extensions

• The h3-pg extension was added.

• The mysql_fdw extension was added.

• The oracle_fdw extension was added.

• The pg_bigm extension was added.

• The pg_hint_plan extension was added.

• The pgAudit extension was added.

• The plprofiler extension was added.

• The plrust extension was added.

• The plv8 extension was added.

This version also includes the following change:

• The pg_tle extension was updated to version 1.1.0.

New extensions

• The aws_commons extension was added.

• The aws_lambda extension was added.

• The aws_s3 extension was added.

• The hypopg extension was added.

• The orafce extension was added.

This version also includes the following change:

• pgvector was updated to version 0.4.4

• aws_commons

• aws_lambda

• aws_s3

• hll

• hypoPG

• mysql_fdw

• oracle_fdw

• orafce

• pg_bigm

• pg_cron

• pg_proctab

• pgaudit

• pghintplan

• pglogical

• plprofiler

• plrust

• plv8

• rdkit

• Fixed a bug allowing the querying of the security invoker views as an unprivileged user.

• Fixed a bug preventing upgrades to PostGIS version 3.4.1.

• Fixed an error with the aws_s3 extension when the Region was not provided.

• The pg_partman extension was updated to version 5.0.1.

• The pg_tle extension was updated to version 1.4.0.

• The pgactive extension was updated to version 2.1.3.

• The pgtap extension was updated to version 1.3.2.

• The pgvector extension was updated to version 0.6.2.

New features and enhancements

• Fixed the multisecond latency on the aws_lambda calls

• Fixed a bug preventing the termination of autovacuum

This version includes the following changes:

• The orafce extension was updated to version 4.9.0.

• The pgactive extension was updated to version 2.1.2.

• The pgvector extension was updated to 0.6.0.

• The plv8 extension was updated to 3.1.10.

• The PostGIS extension was updated to 3.4.1.

New features and enhancements

• Fixed a crash in CatalogCacheComputeHashValue with dblink_connect due to a Null or invalid connection.

• Backported run_as_owner to RPG 15:

  • Backported a security fix for the logical replication apply worker that allows regular table owners to obtain privilege escalation to the subscription owner (an rds_superuser). The logical apply worker mitigates the risk by temporarily switching the role from the subscription owner to the table owner during logical apply.

    In the cases of potential security breaches, the fix will break your existing logical replication if any table in the subscription is owned by a regular user, and there are security-restricted operations attached to the table via triggers or default expressions. We recommend that you carefully examine the operations attached to the table if you notice the logical replication is broken after the upgrade. If all of the operations are as expected and you wish to revert the behavior of the logical replication so your application can continue, you can do so by setting the new parameter rds.run_logical_replication_as_subscription_owner to true. Be aware that by doing so your logical replication will be vulnerable to the aforementioned security risk again.

• Added rds.run_logical_replication_as_subscription_owner to the Amazon RDS parameter group.

• Supported the Amazon SDK version of the aws_s3 extension.

• Blocked the meta-command execution, for example, \copy, \i, and \lo_export, in psql.

• Fixed the overflow in the pg_transport extension.

• Removed the unsupported shared libraries from the engine binary.

This version includes the following changes:

• The plrust extension was updated to version 1.2.7.

• The plv8 extension was updated to version 3.1.9.

New features and enhancements

• Fixed a bug where pg_database_size() with an invalid OID causes a crash.

• Added support for the rds.enable_pgactive parameter in rdsutils to avoid the warning message.

• Exposed RDKit guc param rdkit.morgan_fp_size.

• Fixed the bug where setting TABLESPACE with DEFAULT option in CREATE or ALTER DATABASE fails.

This version includes the following changes:

• The h3-pg extension was updated to version 4.1.3.

• The hll extension was updated to version 2.18.

• The oracle_fdw extension was updated to version 2.6.0.

• The orafce extension was updated to version 4.6.1.

• The pg_cron extension was updated to version 1.6.1.

• The pg_partman extension was updated to version 5.0.0.

• The pg_proctab extension was updated to version 0.0.10.

• The pgactive extension was updated to version 2.1.1.

• The pgtap extension was updated to version 1.3.1.

• The plprofiler extension was updated to version 4.2.4.

• The plrust extension was updated to version 1.2.6.

• The PostGIS extension was updated to version 3.4.0.

• The rdkit extension was updated to version 4.4.0.

• Bug and security fixes for pgactive.

• The pgvector extension was updated to version 0.5.1.

New features and enhancements

• Fixed a bug preventing database owners without the rds_superuser role from being able to create tables in the public schema.

• The pgactive extension was added.

• A new rds.cte_materialize_mode parameter was introduced which controls the materialization behavior of the query of a WITH clause, also known as a Common Table Expression. See WITH Queries for more information. The parameter values include the following:

  • default: The WITH clause will be treated using the engine's default behavior.

  • always: The full output of the query in the WITH clause will be materialized and the output reused in the outer query.

  • never: The query in the WITH clause will be inlined with the outer query if possible. This parameter will also override the MATERIALIZED and NOT MATERIALIZED keywords supplied to the WITH clause.

This version also includes the following changes:

• The mysql_fdw extension was updated to version 2.9.1.

• The pgvector extension was updated to version 0.5.0.

• The plrust extension was updated to version 1.2.5.

• The plv8 extension was updated to version 3.1.8.

• The rdkit extension was updated to version 4.3.0.

New features and enhancements

• Fixed a bug preventing users with the rds_superuser role from creating schemas in databases owned by other users.

• Users with the rds_superuser role can now access toast tables in the pg_toast schema that are owned by other users.

• Fixed an issue where ALTER TABLE took a ShareLock and may cause deadlocks.

This version also includes the following changes:

• The hypopg extension was updated to version 1.4.0.

• The orafce extension was updated to version 4.3.0.

• The pg_tle extension was updated to version 1.1.1.

• The pglogical extension was updated to version 2.4.3.

• The plrust extension was updated to version 1.2.3.

• The PostGIS extension was updated to version 3.3.3.

New features and enhancements

• Improves the performance of plrust

• Fixed a Patroni 2.1.7 restart issue and instead enables replication slot from the disk

This version also includes the following changes:

• The pgvector extension was updated to version 0.4.4.

• The plrust extension was updated to version 1.1.3.

New features and enhancements

• Includes changes to allow rds-superuser to run the pg_stat_reset_slru function

• Fixed a security issue involving rds_sec_override which wasn't reset after the intended usage, allowing unauthorized access to restricted tables

• Added the hypopg extension at version 1.3.1

This version also includes the following changes:

• compat-collation-for-glibc was updated to version 1.8.

• libgeos was updated to version 3.11.2.

• The pg_cron extension was updated to version 1.5.2.

• The pg_partman extension was updated to version 4.7.3.

• The pg_tle extension was updated to version 1.0.4.

• The plrust extension was updated to version 1.1.1.

• The plv8 extension was updated to version 3.1.6.

• The PostGIS extension was updated to version 3.3.2.

New extensions

• The pgvector extension was added.

• The plrust extension was added.

New features and enhancements

• The archive library rds_archive is now used for archiving WAL files instead of archive_command.

• The lz4 and zstd WAL compression methods are now supported.

• By default, the default_toast_compression DB instance parameter is set to lz4.

New extensions

• The pg_walinspect extension version 1.0 was added.

This version also includes the following changes:

• The btree_gist extension was updated to version 1.7.

• The hll extension was updated to version 2.17.

• The mysql_fdw extension was updated to version 2.9.0.

• The pageinspect extension was updated to version 1.11.

• The pg_hint_plan extension was updated to version 1.5.0.

• The pg_repack extension was updated to version 1.4.8.

• The pg_stat_statements extension was updated to version 1.10.

• The pgaudit extension was updated to version 1.7.0.

• The pglogical extension was updated to version 2.4.2.

• The pgrouting extension was updated to version 3.4.1.

• The pllcoffee extension was updated to version 3.1.4.

• The plls extensionwas updated to version 3.1.4.

• The plprofiler extension was updated to version 4.2.1.

• The plv8 extension was updated to version 3.1.4.

• The PostGIS extension was updated to version 3.3.2.

• The tds_fdw extension was updated to version 2.0.3.

• Fixed a bug preventing upgrades to PostGIS version 3.4.1.

• Fixed an error with the aws_s3 extension when the Region was not provided.

• The pg_partman extension was updated to version 5.0.1.

• The pg_tle extension was updated to version 1.4.0.

• The pgactive extension was updated to version 2.1.3.

• The pgtap extension was updated to version 1.3.2.

• The pgvector extension was updated to version 0.6.2.

New features and enhancements

• Fixed the multisecond latency on the aws_lambda calls

• Fixed a bug preventing the termination of autovacuum

This version includes the following changes:

• The orafce extension was updated to version 4.9.0.

• The pg_cron extension was updated to version 1.6.2.

• The pgactive extension was updated to version 2.1.2.

• The pgvector extension was updated to 0.6.0.

• The PostGIS extension was updated to 3.4.1.

New features and enhancements

• Fixed a crash in CatalogCacheComputeHashValue with dblink_connect due to a Null or invalid connection.

• Backported run_as_owner to RPG 14

  • Backported a security fix for the logical replication apply worker that allows regular table owners to obtain privilege escalation to the subscription owner (an rds_superuser). The logical apply worker mitigates the risk by temporarily switching the role from the subscription owner to the table owner during logical apply.

    In the cases of potential security breaches, the fix will break your existing logical replication if any table in the subscription is owned by a regular user, and there are security-restricted operations attached to the table via triggers or default expressions. We recommend that you carefully examine the operations attached to the table if you notice the logical replication is broken after the upgrade. If all of the operations are as expected and you wish to revert the behavior of the logical replication so your application can continue, you can do so by setting the new parameter rds.run_logical_replication_as_subscription_owner to true. Be aware that by doing so your logical replication will be vulnerable to the aforementioned security risk again.

• Added rds.run_logical_replication_as_subscription_owner to the Amazon RDS parameter group.

• Supported the Amazon SDK version of the aws_s3 extension.

• Blocked the meta-command execution, for example, \copy, \i, and \lo_export, in psql.

• Fixed the overflow in the pg_transport extension.

• Removed the unsupported shared libraries from the engine binary.

This version includes the following change:

• The plrust extension was updated to version 1.2.7.

New features and enhancements

• Fixed a bug where pg_database_size() with an invalid OID causes a crash.

• Added support for the rds.enable_pgactive parameter in rdsutils to avoid the warning message.

• Exposed RDKit guc param rdkit.morgan_fp_size.

• Fixed the bug where setting TABLESPACE with DEFAULT option in CREATE or ALTER DATABASE fails.

• Added the pgactive extension.

This version includes the following changes:

• The h3-pg extension was updated to version 4.1.3.

• The hll extension was updated to version 2.18

• The oracle_fdw extension was updated to version 2.6.0.

• The orafce extension was updated to version 4.6.1.

• The pg_cron extension was updated to version 1.6.1.

• The pg_partman extension was updated to version 5.0.0.

• The pg_proctab extension was updated to version 0.0.10.

• The pgtap extension was updated to version 1.3.1.

• The pgvector extension was updated to version 0.5.1.

• The plprofiler extension was updated to version 4.2.4.

• The plrust extension was updated to version 1.2.6.

• The PostGIS extension was updated to version 3.4.0.

• The rdkit extension was updated to version 4.4.0.

New features and enhancements

• A new rds.cte_materialize_mode parameter was introduced which controls the materialization behavior of the query of a WITH clause, also known as a Common Table Expression. See WITH Queries for more information. The parameter values include the following:

  • default: The WITH clause will be treated using the engine's default behavior.

  • always: The full output of the query in the WITH clause will be materialized and the output reused in the outer query.

  • never: The query in the WITH clause will be inlined with the outer query if possible. This parameter will also override the MATERIALIZED and NOT MATERIALIZED keywords supplied to the WITH clause.

This version also includes the following changes:

• The pgvector extension was updated to version 0.5.0.

• The plrust extension was updated to version 1.2.5.

• The rdkit extension was updated to version 4.3.0.

New features and enhancements

• A bug was fixed preventing users with the rds_superuser role from creating schemas in databases owned by other users.

• Users with the rds_superuser role can now access toast tables in the pg_toast schema that are owned by other users.

• Fixed an issue where ALTER TABLE took a ShareLock and may cause deadlocks.

This version also includes the following changes:

• The hypopg extension was updated to version 1.4.0.

• The orafce extension was updated to version 4.3.0.

• The pg_tle extension was updated to version 1.1.1.

• The pglogical extension was updated to version 2.4.3.

• The plrust extension was added at version 1.2.3.

• The PostGIS extension was updated to version 3.3.3

New features and enhancements

• Fixed a Patroni 2.1.7 restart issue and instead enables replication slot from the disk

This version also includes the following change:

• The pgvector extension was updated to version 0.4.4.

New features and enhancements

• Includes changes to allow rds-superuser to run the pg_stat_reset_slru function

• Fixed a security issue involving rds_sec_override which wasn't reset after the intended usage, allowing unauthorized access to restricted tables

• Added extension hypopg version 1.3.1

• Added extension pgvector version 0.4.1

This version also includes the following changes:

• compat-collation-for-glibc was updated to version 1.8.

• The pg_cron extension was updated to version 1.5.2.

• The pg_tle extension was updated to version 1.0.4.

• The pglogical extension was updated to version 2.4.2.

• The PostGIS extension was updated to version 3.3.2.

New features and enhancements

• PostgreSQL version 14.6 added support for the tcn ("triggered change notification") extension which generates notification events on table changes via a trigger function called triggered_change_notification. The tcn extension is useful for applications using drivers which support asynchronous notification. This makes it possible to notify all clients if the contents of a table have been changed, enabling them to take appropriate action in near-real time, such as updating a table cache or information display.

  However, such functionality should only be used with care as it makes all data changes on the table available to all clients (including unprivileged users) through the notification events when they listen on the tcn channel. It is the user’s responsibility to avoid using tcn trigger on a table with sensitive data to avoid information leakage.

• The seg extension version 1.4 was added.

• The tcn extension version 1.0 was added.

• The orafce extension was updated to version 3.24.

• The pgaudit extension was updated to version 1.6.2.

• The pgtap extension was updated to version 1.2.0.

• The rdkit extension was updated to version 4.2.0.

• The PostGIS dependency GDAL was updated to version 3.4.3.

• The wal2json extension was updated to version 2.5.

• The aws_s3 extension was updated to version 1.1.

• The PostGIS extension was updated to version 3.1.7.

• The pg_partman extension was updated to version 4.6.2.

• The pgrouting extension was updated to version 3.2.2.

New features and enhancements

• While this release includes other fixes, a noteworthy fix included in this release is for CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY that can potentially cause silent data corruption of indexes. Amazon RDS has made the fix for the index corruption available since the release of Amazon RDS for PostgreSQL 14.3. This release does not include any RDS specific changes or extension version updates.

New features and enhancements

• This release includes Amazon RDS collations designed to help with data migration from EBCDIC-based systems. For more information, see RDS for PostgreSQL collations for EBCDIC and other mainframe migrations.

• This release includes a fix that was made available in the PostgreSQL out-of-cycle release June 16, 2022 that resolves the CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY issue. The issue affects all community PostgreSQL 14 versions prior to 14.4. For information about how to detect and remediate the issue, see PostgreSQL 14 out-of-cycle release June 16, 2022.

• The pglogical extension was updated to version 2.4.1.

• The pg_hint_plan extension was updated to version 1.4.

• The postgresql-hllextension was updated to version 2.16.

• The mysql_fdw extension version 2.7.0 is added. For more information, see Working with MySQL databases by using the mysql_fdw extension.

• The tds_fdw extension version 2.0.2 is added. For more information, see Working with SQL Server databases by using the tds_fdw extension in the Amazon RDS User Guide.

• The pgaudit extension is updated to 1.6.1. For information about using this extension with RDS for PostgreSQL, see Logging at the session and object level with the pgaudit extension.

• The lo (large objects) module is updated to version 1.1.

• The old_snapshot extension 1.0 is added. If you set old_snapshot_threshold to a value, this extension lets you map transaction ID to a timestamp.

• The amcheck extension was updated to version 1.3.

• The btree_gist extension was updated to version 1.6.

• The cube extension was updated to version 1.5.

• The hstore extension was updated to version 1.8.

• The intarray extension was updated to version 1.5.

• The pageinspect extension was updated to version 1.9.

• The pg_cron extension was updated to version 1.4

• The pg_partman extension was updated to version 4.6.0.

• The pg_repack extension was updated to version 1.4.7.

• The pg_stat_statements extension was updated to version 1.9.

• The pg_trgm extension was updated to version 1.6.

• The pgaudit extension was updated to version 1.6.

• The pgrouting extension was updated to version 3.2.0.

• The postgres_fdw extension was updated to version 1.1.

• Fixed a bug preventing upgrades to PostGIS version 3.4.1.

• The pg_partman extension was updated to version 5.0.1.

• The pg_tle extension was updated to version 1.4.0.

• The pgactive extension was updated to version 2.1.3.

• The pgtap extension was updated to version 1.3.2.

• The pgvector extension was updated to version 0.6.2.

New features and enhancements

• Fixed the multisecond latency on the aws_lambda calls

• Fixed a bug preventing the termination of autovacuum

This version includes the following changes:

• The orafce extension was updated to version 4.9.0.

• The pg_cron extension was updated to version 1.6.2.

• The pgactive extension was updated to version 2.1.2.

• The pgvector extension was updated to 0.6.0.

• The PostGIS extension was updated to 3.4.1.

New features and enhancements

• Fixed a crash in CatalogCacheComputeHashValue with dblink_connect due to a Null or invalid connection.

• Backported run_as_owner to RPG 13:

  • Backported a security fix for the logical replication apply worker that allows regular table owners to obtain privilege escalation to the subscription owner (an rds_superuser). The logical apply worker mitigates the risk by temporarily switching the role from the subscription owner to the table owner during logical apply.

    In the cases of potential security breaches, the fix will break your existing logical replication if any table in the subscription is owned by a regular user, and there are security-restricted operations attached to the table via triggers or default expressions. We recommend that you carefully examine the operations attached to the table if you notice the logical replication is broken after the upgrade. If all of the operations are as expected and you wish to revert the behavior of the logical replication so your application can continue, you can do so by setting the new parameter rds.run_logical_replication_as_subscription_owner to true. Be aware that by doing so your logical replication will be vulnerable to the aforementioned security risk again.

• Added rds.run_logical_replication_as_subscription_owner to the Amazon RDS parameter group.

• Blocked the meta-command execution, for example, \copy, \i, and \lo_export, in psql.

• Fixed the overflow in the pg_transport extension.

• Removed the unsupported shared libraries from the engine binary.

This version includes the following change:

• The plrust extension was updated to version 1.2.7.

New features and enhancements

• Fixed a bug where pg_database_size() with an invalid OID causes a crash.

• Added support for the rds.enable_pgactive parameter in rdsutils to avoid the warning message.

• Exposed RDKit guc param rdkit.morgan_fp_size.

• Fixed the bug where setting TABLESPACE with DEFAULT option in CREATE or ALTER DATABASE fails.

• Added the pgactive extension.

This version includes the following changes:

• The h3-pg extension was updated to version 4.1.3.

• The hll extension was updated to version 2.18

• The oracle_fdw extension was updated to version 2.6.0.

• The orafce extension was updated to version 4.6.1.

• The pg_cron extension was updated to version 1.6.1.

• The pg_proctab extension was updated to version 0.0.10.

• The pgtap extension was updated to version 1.3.1.

• The pgvector extension was updated to version 0.5.1.

• The plprofiler extension was updated to version 4.2.4.

• The plrust extension was updated to version 1.2.6.

• The PostGIS extension was updated to version 3.4.0.

This version includes the following change:

• The pgvector extension was updated to version 0.5.0.

• The plrust extension was updated to version 1.2.5.

New features and enhancements

• A bug was fixed preventing users with the rds_superuser role from creating schemas in databases owned by other users.

• Users with the rds_superuser role can now access toast tables in the pg_toast schema that are owned by other users.

• Fixed an issue where ALTER TABLE took a ShareLock and may cause deadlocks.

This version also includes the following changes:

• hypopg was updated to 1.4.0

• orafce was updated to 4.3.0

• pg_tle was added at version 1.1.1

• pglogical was updated to 2.4.3

• plrust was added at version 1.2.3

• PostGIS was updated to 3.3.3

This version also includes the following change:

• The pgvector extension was updated to version 0.4.4.

New features and enhancements

• Includes changes to allow rds-superuser to run the pg_stat_reset_slru function

• Fixed a security issue involving rds_sec_override which wasn't reset after the intended usage, allowing unauthorized access to restricted tables

• Added extension hypopg version 1.3.1

• Added extension pgvector version 0.4.1

This version also includes the following changes:

• compat-collation-for-glibc was updated to version 1.8

• libcompat was updated to version 1.8

• pg_cron was updated to version 1.5.2

• pglogical was updated to version 2.4.2

• PostGIS was updated to version 3.3.2

• PostgreSQL version 13.9 added support for the tcn ("triggered change notification") extension which generates notification events on table changes via a trigger function called triggered_change_notification. The tcn extension is useful for applications using drivers which support asynchronous notification. This makes it possible to notify all clients if the contents of a table have been changed, enabling them to take appropriate action in near-real time, such as updating a table cache or information display.

  However, such functionality should only be used with care as it makes all data changes on the table available to all clients (including unprivileged users) through the notification events when they listen on the tcn channel. It is the user’s responsibility to avoid using tcn trigger on a table with sensitive data to avoid information leakage.

• The seg extension version 1.3 is added.

• The tcn extension version 1.0 is added.

• The orafce extension is updated to 3.24.

• The pgaudit extension is updated to 1.5.2.

• The pgtap extension is updated to 1.2.0.

• The PostGIS dependency GDAL is updated to 3.4.3.

• The PostGIS dependency PROJ is updated to 8.0.1.

• The wal2json extension is updated to 2.5.

• The aws_s3 extension is updated to 1.1.

• The PostGIS extension is updated to 3.1.7

• The pgRouting extension is updated to 3.1.4

• The pglogical extension is updated to 2.4.1

• The mysql_fdw extension version 2.7.0 is added. For more information, see Working with MySQL databases by using the mysql_fdw extension in the Amazon RDS User Guide.

• The tds_fdw extension version 2.0.2 is added. For more information, see Working with SQL Server databases by using the tds_fdw extension in the Amazon RDS User Guide.

• The pgaudit extension is updated to 1.5.1. For information about using this extension with RDS for PostgreSQL, see Logging at the session and object level with the pgaudit extension in the Amazon RDS User Guide.

• The lo (large objects) module is updated to version 1.1.

• The pg_cron extension is updated to 1.4.1

• The flow_control extension version 1.0 is added in this release.

• The spi module extensions refint, autoinc, inset_username, and moddatetime version 1.0 are added.

• The pgrouting extension is updated to version 3.1.3.

• The pglogical extension is updated to version 2.4.0.

• The PostGIS extension is updated to version 3.1.4, along with the following related extensions:

  • address_standardizer

  • address_standardizer_data_us

  • PostGIS_raster

  • PostGIS_tiger_geocoder

  • PostGIS_topology

• The oracle_fdw extension version 2.3.0 is added. For more information, see Working with Oracle databases by using the oracle_fdw extension in the Amazon RDS User Guide.

• The orafce extension is updated to version 3.15.

• The pg_cron extension is updated to version 1.3.1.

• The pg_partman extension is updated to version 4.5.1.

• The PostGIS extension is updated to version 3.0.3, along with the following related extensions:

  • address_standardizer

  • address_standardizer_data_us

  • PostGIS_raster

  • PostGIS_tiger_geocoder

  • PostGIS_topology

• The aws_lambda extension version 1.0. For more information, see Invoking an Amazon Lambda function from an RDS for PostgreSQL DB instance in the Amazon RDS User Guide.

• The pg_bigm extension version 1.2.

• The bool_plperl extension version 1.0.

• The rds_tools extension version 1.0. For more information, see Checking for users with non-SCRAM passwords .

• The pg_partman extension was updated to version 5.0.1.

• The pgactive extension was updated to version 2.1.3.

• The pgtap extension was updated to version 1.3.2.

• The pgvector extension was updated to version 0.6.2.

New features and enhancements

• Fixed the multisecond latency on the aws_lambda calls

• Fixed a bug preventing the termination of autovacuum

This version includes the following changes:

• The orafce extension was updated to version 4.9.0.

• The pg_cron extension was updated to version 1.6.2.

• The pgactive extension was updated to version 2.1.2.

• The pgvector extension was updated to 0.6.0.

• The PostGIS extension was updated to 3.4.1.

New features and enhancements

• Fixed a crash in CatalogCacheComputeHashValue with dblink_connect due to a Null or invalid connection.

• Backported run_as_owner to RPG 12:

  • Backported a security fix for the logical replication apply worker that allows regular table owners to obtain privilege escalation to the subscription owner (an rds_superuser). The logical apply worker mitigates the risk by temporarily switching the role from the subscription owner to the table owner during logical apply.

    In the cases of potential security breaches, the fix will break your existing logical replication if any table in the subscription is owned by a regular user, and there are security-restricted operations attached to the table via triggers or default expressions. We recommend that you carefully examine the operations attached to the table if you notice the logical replication is broken after the upgrade. If all of the operations are as expected and you wish to revert the behavior of the logical replication so your application can continue, you can do so by setting the new parameter rds.run_logical_replication_as_subscription_owner to true. Be aware that by doing so your logical replication will be vulnerable to the aforementioned security risk again.

• Added rds.run_logical_replication_as_subscription_owner to the Amazon RDS parameter group.

• Blocked the meta-command execution, for example, \copy, \i, and \lo_export, in psql.

• Fixed the overflow in the pg_transport extension.

• Removed the unsupported shared libraries from the engine binary.

New features and enhancements

• Fixed a bug where pg_database_size() with an invalid OID causes a crash.

• Added support for the rds.enable_pgactive parameter in rdsutils to avoid the warning message.

• Exposed RDKit guc param rdkit.morgan_fp_size.

• Fixed the bug where setting TABLESPACE with DEFAULT option in CREATE or ALTER DATABASE fails.

• Added the pgactive extension.

This version includes the following changes:

• The hll extension was updated to version 2.18

• The oracle_fdw extension was updated to version 2.6.0.

• The orafce extension was updated to version 4.6.1.

• The pg_cron extension was updated to version 1.6.1.

• The pg_proctab extension was updated to version 0.0.10.

• The pgtap extension was updated to version 1.3.1.

• The pgvector extension was updated to version 0.5.1.

• The plprofiler extension was updated to version 4.2.4.

• The PostGIS extension was updated to version 3.4.0.

New features and enhancements

• The pgvector extension was added.

New features and enhancements

• A bug was fixed preventing users with the rds_superuser role from creating schemas in databases owned by other users.

• Users with the rds_superuser role can now access toast tables in the pg_toast schema that are owned by other users.

• Fixed an issue where ALTER TABLE took a ShareLock and may cause deadlocks.

This version also includes the following changes:

• The orafce extension was updated to version 4.3.0.

• The pglogical extension was updated to version 2.4.3.

• The PostGIS extension was updated to version 3.3.3.

New features and enhancements

• Fixed a security issue involving rds_sec_override which wasn't reset after the intended usage, allowing unauthorized access to restricted tables

This version also includes the following changes:

• compat-collation-for-glibc was updated to version 1.8

• pg_cron was updated to version 1.5.2

• pglogical was updated to version 2.4.2

• PostGIS was updated to version 3.3.2

• PostgreSQL version 12.13 added support for the tcn ("triggered change notification") extension which generates notification events on table changes via a trigger function called triggered_change_notification. The tcn extension is useful for applications using drivers which support asynchronous notification. This makes it possible to notify all clients if the contents of a table have been changed, enabling them to take appropriate action in near-real time, such as updating a table cache or information display.

  However, such functionality should only be used with care as it makes all data changes on the table available to all clients (including unprivileged users) through the notification events when they listen on the tcn channel. It is the user’s responsibility to avoid using tcn trigger on a table with sensitive data to avoid information leakage.

• The seg extension version 1.3 is added.

• The tcn extension version 1.0 is added.

• The orafce extension is updated to 3.24.

• The pgaudit extension is updated to 1.4.3.

• The pgtap extension is updated to 1.2.0.

• The PostGIS dependency GDAL is updated to 3.4.3.

• The PostGIS dependency PROJ is updated to 7.0.1.

• The wal2json extension is updated to 2.5.

• The aws_s3 extension is updated to 1.1.

• The PostGIS extension is updated to 3.1.7

• The pgRouting extension is updated to 3.0.6

• The pglogical extension is updated to 2.4.1.

• The pgaudit extension is updated to 1.4.2. For information about using this extension with RDS for PostgreSQL, see Logging at the session and object level with the pgaudit extension.

• The lo (large objects) module is updated to version 1.1.

• The pg_cron extension is updated to 1.4.1

• The pg_hint_plan extension is updated to 1.3.7.

• The pgRouting extension is updated to version 3.0.5.

• The pglogical extension is updated to version 2.4.0.

• The PostGIS extension is updated to version 3.1.4, along with the following related extensions:

  • address_standardizer

  • address_standardizer_data_us

  • PostGIS_raster

  • PostGIS_tiger_geocoder

  • PostGIS_topology

• The oracle_fdw extension version 2.3.0 is added. For more information, see Working with Oracle databases by using the oracle_fdw extension in the Amazon RDS User Guide.

• The orafce extension is updated to version 3.15.

• The pg_cron extension is updated to version 1.3.1.

• The pg_partman extension is updated to version 4.5.1.

• The PostGIS extension is updated to version 3.0.3, along with the following related extensions:

  • address_standardizer

  • address_standardizer_data_us

  • PostGIS_raster

  • PostGIS_tiger_geocoder

  • PostGIS_topology

• The aws_lambda extension version 1.0 is added. For more information, see Invoking an Amazon Lambda function from an RDS for PostgreSQL DB instance in the Amazon RDS User Guide.

• The pg_bigm extension version 1.2 is added.

• The PostGIS extension is updated to version 3.0.2.

• Added the pg_partman extension version 4.4.0. For more information, see Managing PostgreSQL partitions with the pg_partman extension in the Amazon RDS User Guide.

• Added the pg_cron extension version 1.3.0. For more information, see Scheduling maintenance with the PostgreSQL pg_cron extension in the Amazon RDS User Guide.

• Added the pg_proctab extension version 0.0.9

• Added the rdkit extension version 3.8

• Upgraded the aws_s3 extension to version 1.1.

• Upgraded the pglogical extension to version 2.3.2

• Upgraded the wal2json extension to version 2.3

• Upgraded the pg_hint_plan extension to version 1.3.5.

• Upgraded the pglogical extension to version 2.3.1.

New features and enhancements

• Backported run_as_owner to RPG 11:

  • Backported a security fix for the logical replication apply worker that allows regular table owners to obtain privilege escalation to the subscription owner (an rds_superuser). The logical apply worker mitigates the risk by temporarily switching the role from the subscription owner to the table owner during logical apply.

    In the cases of potential security breaches, the fix will break your existing logical replication if any table in the subscription is owned by a regular user, and there are security-restricted operations attached to the table via triggers or default expressions. We recommend that you carefully examine the operations attached to the table if you notice the logical replication is broken after the upgrade. If all of the operations are as expected and you wish to revert the behavior of the logical replication so your application can continue, you can do so by setting the new parameter rds.run_logical_replication_as_subscription_owner to true. Be aware that by doing so your logical replication will be vulnerable to the aforementioned security risk again.

• Added rds.run_logical_replication_as_subscription_owner to the Amazon RDS parameter group.

• Blocked the meta-command execution, for example, \copy, \i, and \lo_export, in psql.

• Fixed the overflow in the pg_transport extension.

• Removed the unsupported shared libraries from the engine binary.

New features and enhancements

• Fixed a bug where pg_database_size() with an invalid OID causes a crash.

• Added support for the rds.enable_pgactive parameter in rdsutils to avoid the warning message.

• Exposed RDKit guc param rdkit.morgan_fp_size.

• Fixed the bug where setting TABLESPACE with DEFAULT option in CREATE or ALTER DATABASE fails.

• Added the pgactive extension.

This version includes the following changes:

• The hll extension was updated to version 2.18

• The orafce extension was updated to version 4.6.1.

• The pg_proctab extension was updated to version 0.0.10.

• The pgtap extension was updated to version 1.3.1.

• The plprofiler extension was updated to version 4.2.4.

New features and enhancements

• A bug was fixed preventing users with the rds_superuser role from creating schemas in databases owned by other users.

• Users with the rds_superuser role can now access toast tables in the pg_toast schema that are owned by other users.

• Fixed an issue where ALTER TABLE took a ShareLock and may cause deadlocks.

This version also includes the following changes:

• The orafce extension was updated to version 4.3.0.

• The pglogical extension was updated to version 2.4.3.

• The PostGIS extension was updated to version 3.3.3.

New features and enhancements

• Fixed a security issue involving rds_sec_override which wasn't reset after the intended usage, allowing unauthorized access to restricted tables

This version also includes the following changes:

• compat-collation-for-glibc was updated to version 1.8

• pglogical was updated to version 2.4.2

• PostGIS was updated to version 3.3.2

• PostgreSQL version 11.18 added support for the tcn ("triggered change notification") extension which generates notification events on table changes via a trigger function called triggered_change_notification. The tcn extension is useful for applications using drivers which support asynchronous notification. This makes it possible to notify all clients if the contents of a table have been changed, enabling them to take appropriate action in near-real time, such as updating a table cache or information display.

  However, such functionality should only be used with care as it makes all data changes on the table available to all clients (including unprivileged users) through the notification events when they listen on the tcn channel. It is the user’s responsibility to avoid using tcn trigger on a table with sensitive data to avoid information leakage.

• The seg extension version 1.3 is added.

• The tcn extension version 1.0 is added.

• The orafce extension is updated to 3.24.

• The pgaudit extension is updated to 1.3.4.

• The pgtap extension is updated to 1.2.0.

• The PostGIS dependency GDAL is updated to 3.4.3.

• The PostGIS dependency PROJ is updated to 7.0.1.

• The wal2json extension is updated to 2.5.

• The aws_s3 extension is updated to 1.1.

• The PostGIS extension is updated to 3.1.7

• The pglogical extension is updated to 2.4.1.

• The aws_commons extension is updated to 1.2.

• The pgaudit extension is updated to 1.3.3. For information about using this extension with RDS for PostgreSQL, see Logging at the session and object level with the pgaudit extension.

• The lo module is updated to version 1.1.

• The pg_hint_plan extension is updated to 1.3.7.

• The pgrouting extension is updated to version 2.6.3.

• The pglogical extension is updated to version 2.4.0.

• The PostGIS extension is updated to version 3.1.4, along with the following related extensions:

  • address_standardizer

  • address_standardizer_data_us

  • PostGIS_raster

  • PostGIS_tiger_geocoder

  • PostGIS_topology

• The orafce extension is updated to version 3.15.

• The pg_bigm extension version 1.2.

• Added the aws_s3 extension version 1.1

• Added the pg_proctab extension version 0.0.9

• Upgraded the pgaudit extension to version 1.3.1

• Upgraded the pglogical extension to version 2.2.2

• Added the rdkit extension version 3.8

• Upgraded the pg_hint_plan extension to version 1.3.5.

• Upgraded the pgTAP extension to version 1.1.0.

• Added the plprofiler extension.

• Added to shared_preload_libraries support for pg_prewarm to start automatically.

• A new extension pg_transport is added.

• The extension aws_s3 has been updated to support virtual-hosted style requests. For more information, see Amazon S3 path deprecation plan – The rest of the story.

• The PostGIS extension is updated to version 2.5.2.

• A new pgTAP extension version 1.0.

• Support for Amazon S3 import. For more information, see Importing Amazon S3 data into an RDS for PostgreSQL DB instance in the Amazon RDS User Guide.

• Multiple major version upgrade is available to PostgreSQL 11.2 from certain previous PostgreSQL versions. For more information, see Choosing a major version upgrade for PostgreSQL in the Amazon RDS User Guide.

• Partitioning – Partitioning improvements include support for hash partitioning, enabling creation of a default partition, and dynamic row movement to another partition based on the key column update.

• Performance – Performance improvements include parallelism while creating indexes, materialized views, hash joins, and sequential scans to make the operations perform better.

• Stored procedures – SQL stored procedures now added support embedded transactions.

• Support for Just-In-Time (JIT) capability – RDS for PostgreSQL 11 instances are created with JIT capability, speeding evaluation of expressions. To enable JIT capability, set the jit parameter to 1 in the PostgreSQL parameter group for the database.

• Segment size – The write-ahead logging (WAL) segment size has been changed from 16 MB to 64 MB.

• Autovacuum improvements – To provide valuable logging, the parameter rds.force_autovacuum_logging is ON by default in conjunction with the log_autovacuum_min_duration parameter set to 10 seconds. To increase autovacuum effectiveness, the values for the autovacuum_max_workers and autovacuum_vacuum_cost_limit parameters are computed based on host memory capacity to provide larger default values.

• Improved transaction timeout – The parameter idle_in_transaction_session_timeout is set to 24 hours. Any session that has been idle more than 24 hours is terminated.

• Performance metrics – The pg_stat_statements extension is included in shared_preload_libraries by default. This avoids having to reboot the instance immediately after creation. However, this functionality still requires you to run the statement CREATE EXTENSION pg_stat_statements;. Also, track_io_timing is enabled by default to add more granular data to pg_stat_statements.

• The tsearch2 extension is no longer supported – If your application uses tsearch2 functions, update it to use the equivalent functions provided by the core PostgreSQL engine. For more information about the tsearch2 extension, see PostgreSQL tsearch2.

• The chkpass extension is no longer supported – For more information about the chkpass extension, see PostgreSQL chkpass.

• Extension updates for RDS for PostgreSQL 11.1 include the following:

  • pgaudit is updated to 1.3.0

  • pg_hint_plan is updated to 1.3.2

  • pglogical is updated to 2.2.1

  • plcoffee is updated to 2.3.8

  • plv8 is updated to 2.3.8

  • PostGIS is updated to 2.5.1

  • prefix is updated to 1.2.8

  • wal2json is updated to hash 9e962bad

• PostgreSQL version 10.23 added support for the tcn ("triggered change notification") extension which generates notification events on table changes via a trigger function called triggered_change_notification. The tcn extension is useful for applications using drivers which support asynchronous notification. This makes it possible to notify all clients if the contents of a table have been changed, enabling them to take appropriate action in near-real time, such as updating a table cache or information display.

  However, such functionality should only be used with care as it makes all data changes on the table available to all clients (including unprivileged users) through the notification events when they listen on the tcn channel. It is the user’s responsibility to avoid using tcn trigger on a table with sensitive data to avoid information leakage.

• The seg extension version 1.1 is added.

• The tcn extension version 1.0 is added.

• The orafce extension is updated to 3.24.

• The pgaudit extension is updated to 1.2.4.

• PostGIS dependency GDAL is updated to 3.4.3.

• PostGIS dependency PROJ is updated to 7.0.1.

• The wal2json extension is updated to 2.5.

• The aws_s3 extension is updated to 1.1.

• The PostGIS extension is updated to 3.1.7

• The pglogical extension is updated to 2.4.1.

• The aws_commons extension is updated to 1.2.

• The pgaudit extension is updated to 1.2.3. For information about using this extension with RDS for PostgreSQL, see Logging at the session and object level with the pgaudit extension in the Amazon RDS User Guide.

• The lo module is updated to version 1.1.

• The pg_hint_plan extension is updated to 1.3.6.

• The pgrouting extension is updated to version 2.5.5.

• The pglogical extension is updated to version 2.4.0.

• The PostGIS extension is updated to version 3.1.4, along with the following related extensions:

  • address_standardizer

  • address_standardizer_data_us

  • PostGIS_raster

  • PostGIS_tiger_geocoder

  • PostGIS_topology

• The orafce extension is updated to version 3.15.

• Added the aws_s3 extension version 1.1. For more information, see Exporting data from an RDS for PostgreSQL DB instance to Amazon S3 in the Amazon RDS User Guide.

• Upgraded the pgaudit extension to version 1.2.1

• Upgraded the pglogical extension to version 2.2.2

• Upgraded the wal2json extension to version 2.3

• Upgraded the pg_hint_plan extension to version 1.3.5.

• Added the plprofiler extension.

• The aws_s3 extension is updated to support virtual-hosted style requests. For more information, see Amazon S3 path deprecation plan – The rest of the story.

• The The PostGIS extension is updated to version 2.5.2.

• Support for Amazon S3 import. For more information, see Importing Amazon S3 data into an RDS for PostgreSQL DB instance in the Amazon RDS User Guide.

• Multiple major version upgrade is available to PostgreSQL 10.7 from certain previous PostgreSQL versions. For more information, see Choosing a major version upgrade for PostgreSQL in the Amazon RDS User Guide.

• A new rds.restrict_password_commands parameter and a new rds_password role have been introduced. When the rds.restrict_password_commands parameter is enabled, only users who have the rds_password role can make user password and password expiration changes. By restricting password-related operations to a limited set of roles, you can implement policies such as password complexity requirements from the client side. The rds.restrict_password_commands parameter is static, so it requires a database restart to change it. For more information, see Restricting password management in the Amazon RDS User Guide.

• The logical decoding plugin wal2json has been updated to commit 9e962ba.

• Support for the pglogical extension version 2.2.0. Prerequisites for using this extension are the same as the prerequisites for using logical replication for PostgreSQL as described in Performing logical replication for Amazon RDS for PostgreSQL in the Amazon RDS User Guide.

• Support for the pg_similarity extension version 1.0.

• Support for the pageinspect extension version 1.6.

• Support for the libprotobuf extension version 1.3.0 for the PostGIS component.

• An update for the pg_hint_plan extension to version 1.3.1.

• An update for the wal2json extension to version 01c5c1e.

• Support for PostgreSQL 10 Logical Replication using the native publication and subscription framework. RDS for PostgreSQL databases can function as both publishers and subscribers. You can specify replication to other PostgreSQL databases at the database-level or at the table-level. With logical replication, the publisher and subscriber databases need not be physically identical (block-to-block) to each other. This allows for use cases such as data consolidation, data distribution, and data replication across different database versions for 10.4 and above. For more information, see Performing logical replication for Amazon RDS for PostgreSQL in the Amazon RDS User Guide.

• The temporary file size limitation is user-configurable. You require the rds_superuser role to modify the temp_file_limit parameter.

• Update of the GDAL library, which is used by the PostGIS extension. See Managing spatial data with the PostGIS extension in the Amazon RDS User Guide.

• Update of the ip4r extension to version 2.1.1.

• Update of the pg_repack extension to version 1.4.3. See Working with the pg_repack extension in the Amazon RDS User Guide.

• Update of the plv8 extension to version 2.1.2.

• Declarative table partitioning – PostgreSQL 10 adds table partitioning to SQL syntax and native tuple routing.

• Parallel queries – When you create a new PostgreSQL 10.1 instance, parallel queries are enabled for the default.postgres10 parameter group. The parameter max_parallel_workers_per_gather is set to 2 by default, but you can modify it to support your specific workload requirements.

• Support for the international components for unicode (ICU) – You can use the ICU library to provide explicitly versioned collations. Amazon RDS for PostgreSQL 10.1 is compiled with ICU version 60.2. For more information about ICU implementation in PostgreSQL, see Collation support.

• Huge pages – Huge pages is a feature of the Linux kernel that uses multiple page size capabilities of modern hardware architectures. Amazon RDS for PostgreSQL supports huge pages with a global configuration parameter. When you create a new PostgreSQL 10.1 instance with RDS, the huge_pages parameter is set to "on" for the default.postgres10 parameter group. You can modify this setting to support your specific workload requirements.

• Extension plv8 update – plv8 is a procedural language that you can use to write functions in JavaScript that you can then call from SQL. This release of PostgreSQL supports version 2.1.0 of plv8.

• Renaming of xlog and location – In PostgreSQL version 10 the abbreviation "xlog" has changed to "wal", and the term "location" has changed to "lsn". For more information, see https://www.postgresql.org/docs/10/static/release-10.html#id-1.11.6.8.4.

• tsearch2 extension – Amazon RDS continues to provide the tsearch2 extension in PostgreSQL version 10, but is to remove it in the next major version release. If your application uses tsearch2 functions update it to use the equivalent functions the core engine provides. For more information see tsearch2 in the PostgreSQL documentation.

• The pg_hint_plan extension is updated to 1.2.7.

• The pglogical extension is updated to version 2.4.0.

• The PostGIS extension is updated to version 2.5.5, along with the following related extensions:

  • address_standardizer

  • address_standardizer_data_us

  • PostGIS_tiger_geocoder

  • PostGIS_topology

• The orafce extension is updated to version 3.15.

• Upgraded the pgaudit extension to version 1.1.2

• Upgraded the pglogical extension to version 2.2.2

• Upgraded the wal2json extension to version 2.3

• Upgraded the pg_hint_plan extension to version 1.2.6.

• Support for the pglogical extension version 2.2.0. Prerequisites for using this extension are the same as the prerequisites for using logical replication for PostgreSQL as described in Performing logical replication for Amazon RDS for PostgreSQL in the Amazon RDS User Guide.

• Support for the pg_similarity extension version 2.2.0.

• An update for the wal2json extension to version 01c5c1e.

• An update for the pg_hint_plan extension to version 1.2.3.

• The temporary file size limitation is user-configurable. You require the rds_superuser role to modify the temp_file_limit parameter.

• Update of the GDAL library, which is used by the PostGIS extension. See Working with the PostGIS extension in the Amazon RDS User Guide.

• Update of the ip4r extension to version 2.1.1.

• Update of the pgaudit extension to version 1.1.1. See Logging at the session and object level with the pgaudit extension in the Amazon RDS User Guide.

  Update of the pg_repack extension to version 1.4.3. See Working with the pg_repack extension in the Amazon RDS User Guide.

• Update of the plv8 extension to version 2.1.2.

• Supports the orafce extension, version 3.6.1. This extension contains functions that are native to commercial databases, and can be helpful if you are porting a commercial database to PostgreSQL. For more information about using orafce with Amazon RDS, see Using functions from the orafce extensionin the Amazon RDS User Guide.

• Supports the prefix extension, version 1.2.6. This extension provides an operator for text prefix searches. For more information about prefix, see the prefix project on GitHub.

• Supports version 2.3.4 of PostGIS, version 2.4.2 of pgrouting, and an updated version of wal2json.

• Supports the extension pg_repack version 1.4.0. You can use this extension to remove bloat from tables and indexes. For more information on using pg_repack with Amazon RDS, see Reducing bloat in tables and indexes with the pg_repack extension in the Amazon RDS User Guide.

• Supports the extension pgaudit version 1.1.0. This extension provides detailed session and object audit logging. For more information on using pgaudit with Amazon RDS, see Logging at the session and object level with the pgaudit extension in the Amazon RDS User Guide.

• Supports wal2json, an output plugin for logical decoding.

• Supports the auto_explain extension. You can use this extension to log execution plans of slow statements automatically. The following example shows how to use auto_explain from within an Amazon RDS PostgreSQL session:

  LOAD '$libdir/plugins/auto_explain';

  For more information on using auto_explain, see the PostgreSQL documentation.

• PostGIS version 2.3.2

• pg_freespacemap version 1.1–Provides a way to examine the free space map (FSM). This extension provides an overloaded function called pg_freespace. The functions show the value recorded in the free space map for a given page, or for all pages in the relation.

• pg_hint_plan version 1.1.3– Provides control of execution plans by using hinting phrases at the beginning of SQL statements.

• log_fdw version 1.0–Using this extension from Amazon RDS, you can load and query your database engine log from within the database. For more information, see Using the log_fdw extension to access the DB log using SQL in the Amazon RDS User Guide.

• With this version release, you can now edit the max_worker_processes parameter in a DB parameter group.

• Parallel query processing: Supports parallel processing of large read-only queries, allowing sequential scans, hash joins, nested loops, and aggregates to be run in parallel. By default, parallel query processing isn't enabled. To enable parallel query processing, set the parameter max_parallel_workers_per_gather to a value larger than zero.

• Updated postgres_fdw extension: Supports remote JOINs, SORTs, UPDATEs, and DELETE operations.

• plv8 update: Provides version 1.5.3 of the plv8 language.

• PostGIS version update: Supports POSTGIS="2.3.0 r15146" GEOS="3.5.0-CAPI-1.9.0 r4084" PROJ="Rel. 4.9.2, 08 September 2015" GDAL="GDAL 2.1.1, released 2016/07/07" LIBXML="2.9.1" LIBJSON="0.12" RASTER

• Vacuum improvement: Avoids scanning pages unnecessarily during vacuum freeze operations.

• Full-text search support for phrases: Supports the ability to specify a phrase-search query in tsquery input using the new operators <-> and <N>.

• Two new extensions are supported:

  • bloom, an index access method based on Bloom filters

  • pg_visibility, which provides a means for examining the visibility map and page-level visibility information of a table.

• With the release of version 9.6.2, you can now edit the max_worker_processes parameter in a PostgreSQL version 9.6.1 DB parameter group.