Amazon Aurora PostgreSQL updates

General enhancements

• Fixed a performance degradation issue in PLV8 extension.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue where pg_stat_statements can block minor version upgrade during ZDP.

• Fixed an issue where a logical replication slot would no longer emit changes due to an overly strict data consistency check.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

New features

• Added support for the HypoPG extension at version 1.4.0.

• Added support for the h3-pg extension and the h3-postgis extension at version 4.1.3.

• Added support for aurora_compute_plan_id parameter which is turned on by default in an Aurora PostgreSQL DB Cluster and DB Parameter Group. For more information, see Monitoring query execution plans for Aurora PostgreSQL.

• The rds.rds_superuser_reserved_connections parameter has been deprecated in Aurora 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.

General enhancements

• Deprecated support for ssl protocols: TLSv1.0 and TLSv1.1.

Additional improvements and enhancements

Updated the following extensions:

• postgis to version 3.4.0

• PgLogical to version 2.4.4

• PgCron to version 1.6

• orafce to version 4.6.0

• pg_hint_plan to version 1.6.0

• plv8 to version 3.1.8

• oracle_fdw to version 2.6.0

• MySQL_FDW to version 2.9.1

• Hll to version 2.18

• RDKit to version 4.4

• aws_s3 to version 1.2

• prefix to version 1.2.10

• pg_similarity to version 1.0

• pgdam to version 1.7

• pg_proctab to version 0.0.10

• pg_tle to version 1.2.0

• pg_vector to version 0.5.1

• PgAudit to version 16.0

• plprofiler to version 4.2.4

• pg_partman to version 4.7.3

• pgTAP to version 1.3.0

Migrating to Aurora PostgreSQL 16

The following minumum extension versions are required for major version upgrade to Aurora PostgreSQL 16:

• PostGIS version 3.1

• PgRouting version 3.0.5

• Rdkit version 4.2

Unsupported Features

• Aurora PostgreSQL 16.1 doesn't currently support logical decoding on Aurora Read Replicas.

Differences between PostgreSQL 16 and Aurora PostgreSQL 16

In Aurora PostgreSQL 16.1, the newly introduced pg_stat_io view has two additional I/O contexts:

• index: I/O operations performed during index creation.

• walreplay: I/O operations performed by the wal replay process on Aurora read replicas.

• autovacuum launcher

• autovacuum worker

• bulkwrite

• index

• vacuum

General enhancements

• Deprecated support for SSL protocols: TLS 1.0 and TLS 1.1

Additional improvements and enhancements

Updated the following extensions:

• aws_s3 to version 1.2

• oracle_fdw to version 2.6.0

• orafce to version 4.6.0

• pg_cron to version 1.6.0

• pg_hint to version 1.6.0

• pg_proctab to version 0.0.10

• pg_tle to version 1.2.0

• pglogical to version 2.4.4

• pgvector to version 0.5.0

• plv8 to version 3.1.7

• PostGIS to version 3.4.0

• prefix to version 1.2.0

• RDKit to version 4.3.0

• aws_lambda

• hll

• pg_bigm

• pgAudit

• plprofiler

• rds_activity_stream

Unsupported Features

• Aurora PostgreSQL 16.0 does not currently support logical decoding on Aurora read replicas.

• Aurora PostgreSQL 16.0 does not currently support Aurora PostgreSQL Query Plan Management.

Differences between PostgreSQL 16 and Aurora PostgreSQL 16

In Aurora PostgreSQL 16.0, the newly introduced pg_stat_io view has two additional I/O contexts:

• index: I/O operations performed during index creation.

• walreplay: I/O operations performed by the wal replay process on Aurora read replicas.

• autovacuum launcher

• autovacuum worker

• bulkwrite

• index

• vacuum

General enhancements

• Fixed a performance degradation issue in PLV8 extension.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue where pg_stat_statements can block minor version upgrade during ZDP.

• Fixed an issue where a logical replication slot would no longer emit changes due to an overly strict data consistency check.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

New features

• Amazon Bedrock integration – By using the Amazon Aurora machine learning extension with your Aurora PostgreSQLDB cluster, you can now use Amazon Bedrock foundational AI models.

• Using Active Directory security groups for Aurora PostgreSQL access control – Add group role authentication support using Amazon Directory Service for Microsoft Active Directory with the new pg_ad_mapping extension.

• Delegated Extension Support – This feature allows delegating extension management to lower privileged user with the new rds_extension role.

• Added support for aurora_compute_plan_id parameter which is turned on by default in an Aurora PostgreSQL DB Cluster and DB Parameter Group. For more information, see Monitoring query execution plans for Aurora PostgreSQL.

• Query Plan Management (QPM) enhancements:

  • Plan outlines will be updated to the latest format version as part of the update_plan_hash action for apg_plan_mgmt.validate_plans().

  • Support was added for parallel append enforcement as a part of parallel query enforcement.

• Added support for the HypoPG extension at version 1.4.0.

• Added support for the h3-pg extension and the h3-postgis extension at version 4.1.3.

High priority enhancements

• Fixed an issue which may cause a reboot when logically replicating changes in the presence of concurrently-running DDL or canceled sub-transactions

• Fixed an issue which may cause an Aurora replica to reboot when reading a page which was modified during WAL replay

• Fixed an issue where if a specific volume metadata is invalid on a source cluster, it will remain invalid on a cloned cluster. Since the clone cluster uses a new volume, the metadata will now be recreated.

• Fixed a bug that may cause an engine crash during zero-downtime patching (ZDP)

• Introduced a new parameter, rds.enable_memory_management, which is used to enable and disable the improved memory management feature.

• Improved index scan query performance by skipping unnecessary B-tree page reads when a composite index is used with large data sets.

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General enhancements

• Fixed an issue which caused the AuroraGlobalDBRPOLag metric to be zero when the rds.global_db_rpo parameter was not set.

• Fixed an issue which may cause an Aurora replica to reboot while reconnecting with the writer DB instance.

• Added support for the rdkit.morgan_fp_size parameter

• rds-superuser can now run the pg_stat_reset_slru function

• Fixed an issue where MultiXact SLRU accesses were not credited to the correct pg_stat_slru category.

• Fixed an issue which may cause unused WAL segements to not be properly removed

• Fixed an issue where pglogical does not correctly pass-through replication origin data when using the binary output format

• rds_superuser can now execute ALTER COLLATION to refresh the collation version of a locale in the catalog.

• Fixed a crash in dblink and postgres_fdw extensions due to invalid connections

• Fixed an issue where the aws_s3 extension can import HTTP error responses into the table

• Fixed an issue which may cause an Aurora Replica instance with Optimized Reads to reboot while reconnecting with the writer DB instance.

• Fixed an issue which may cause an Aurora replica with Optimized Reads to reboot while caching a page to tiered cache.

Additional improvements and enhancements

• Updated the following extensions:

  • mysql_fdw to version 2.9.1

  • Oracle_fdw to version 2.6.0

  • Orafce to version 4.6.0

  • pg_cron to version 1.6.0

  • pg_hint_plan to version 1.5.1

  • pg_proctab to version 0.0.10

  • pg_tle to version 1.2.0

  • plv8 to version 3.1.8

  • PostGIS to version 3.4.0

  • prefix to version 1.2.10

  • RDKit to version 4.4.0 (Release_2023_09_1)

General enhancements

• Fixed a performance degradation issue in PLV8 extension.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue where pg_stat_statements can block minor version upgrade during ZDP.

• Fixed an issue where a logical replication slot would no longer emit changes due to an overly strict data consistency check.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

High priority enhancements

• Fixed an issue which may cause a reboot when logically replicating changes in the presence of concurrently-running DDL or canceled sub-transactions

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

High priority enhancements

• Improved the index scan query performance by skipping unnecessary B-tree page reads when a composite index is used with large data sets

• Fixed an issue with index scan queries that, in rare cases, could lead to database instance restarts

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue that could result in read replica lag due to stale metadata

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

New features

• Added support for mysql_fdw version 2.9.0

• Added support in the aws_s3 extension for exporting to an S3 bucket encrypted with a customer managed KMS key

• Improved the availability of Aurora replicas in the global DB secondary clusters

• Added support for query plan capture on Aurora replicas

• Added support for query plan enforcement with materialize nodes

• Added support for query plan enforcement with parallel query operators

• Query plans under a given cost threshold will not be captured

High priority enhancements

• Fixed an issue which could cause the database to fail to start up during database recovery

• Included optimizations to improve the time to scale up in Aurora Serverless v2 instances

General enhancements

• Fixed an issue in the aws_s3 extension where the number of rows exported is incorrectly reported when the total number exceeds 2 billion

• Provided options to configure timeouts in the aws_s3 extension. By setting the following parameters (GUCs), customers will now be able to change the timeout thresholds for imports from S3:

  • aws_s3.curlopt_low_speed_limit

  • aws_s3.curlopt_low_speed_time

• Prevented instance creation failure in some edge cases

• Improved the performance of replay of commit transaction operations on Aurora replicas

• Fixed an issue where, in rare cases, an import from the aws_s3 extension fails to complete

• Updated the GEOS library for PostGIS to version 3.12.0

• Improved Aurora Serverless v2 database memory scaling which reduces the overall database instance scale time

• Added the WAIT_EVENT_Aurora_CLUSTER_CACHE_MANAGER_SENDER wait event to denote wait times in the cluster cache manager sender

• Added the WAIT_EVENT_Aurora_SERVERLESS_MONITORING_MAIN wait event to denote wait times in Aurora Serverless resource monitoring

• Improved the handling of invalid non-persisted metadata during reads from storage on read replicas

• Fixed an issue where the database may crash during the start of a logical replication slot

• Increased the limit for pg_cron cron.max_running_jobs parameter from 100 to 1000

• The pgAudit pgaudit.log_statement parameter is now modifiable

• Fixed a bug in CREATE TABLE command to handle table name starting with '#' correctly.

Additional improvements and enhancements

• Updated the following extensions:

  • orafce to version 4.3.0

  • pg_logical to version 2.4.3

  • pg_tle to version 1.1.1

  • pgvector to version 0.5.0

  • plv8 to version 3.1.6

  • PostGIS to version 3.3.3

  • RDKit to version 4.3

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue that would cause a logical replication slot to transiently error out in the presence of aborted subtransactions and DDL.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

High priority enhancements

• Improved the index scan query performance by skipping unnecessary B-tree page reads when a composite index is used with large data sets

• Fixed an issue with index scan queries that, in rare cases, could lead to database instance restarts

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue that could result in read replica lag due to stale metadata

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39418

  • CVE-2023-39417

High priority enhancements

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads

• Fixed an issue which can cause vacuum operations to become blocked after the restart of an Aurora replica

• Fixed an issue that would cause a crash when executing the COPY FROM command

• Fixed an issue that would cause high CPU usage and prevent new connections

• Fixed an issue where UPDATE and DELETE from a table with foreign key could fail unexpectedly with "ERROR: 40001: could not serialize access due to concurrent update when using Serializable snapshot"

General enhancements

• Introduced diagnostics for the transient metadata used for I/O

• Fixed an issue that prevented the enablement of improved memory management in certain scenarios in Aurora PostgreSQL 15.3

New features

• This release contains memory management improvements which increase database stability and availability by proactively preventing issues caused by insufficient memory. For more information, see Improved memory management in Aurora PostgreSQL.

• Added support for the pgvector extension version 0.4.1.

High priority enhancements

• Fixed an issue with the subtransaction metadata handling when performing a survivable reader reconnect

• Fixed an issue during ZDP which is related to the extension environment variables

• Addressed a transient error during logical replication that caused a process to incorrectly calculate that it had encountered an unexpected page

• Fixed an issue which causes a period of unavailability due to a partially created replication origin state file

General enhancements

• Addressed an issue where the computing query identifier displayed a warning, "WARNING: unrecognized node type: 378"

• Addressed an issue that caused the initial data sync of a relation to become blocked due to the premature removal of the logical replication slot on the publisher

• Added a new function, aurora_stat_memctx_usage(), to show backend memory use breakdown at a Postgres memory context level

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters (GUCs), customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms

  • aws_lambda.request_timeout_ms

• Fixed an issue with the calculation of the AuroraReplicaLag metric

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots

• Further reduced the database downtime during ZDP

• Fixed a bug which can cause unavailability during ZDP

• Fixed an issue which caused pg_ls_waldir() to return "ERROR: could not stat file"

• Added support for TLS 1.3 with ciphers TLS_AES_128_GCM_SHA256 and TLS_AES_256_GCM_SHA384

• Addressed an issue that blocked a major version upgrade on the Aurora replica of an RDS for PostgreSQL DB instance

• Fixed an issue that could prevent scaling in Aurora Serverless v2 instances

• Fixed an issue in logical replication which, in rare cases, can cause a period of unavailability due to the incorrect subtransaction metadata

• Fixed an issue in the pg_vector extension where, in rare cases, infinite or NAN values caused a crash during the index creation

• Fixed an issue to improve the performance

• Upgraded GEOS to version 3.11.2

• Upgraded pg_cron to version 1.5

• Upgraded pg_partman to version 4.7.3

• Upgraded pg_tle to version 1.0.3

• Upgraded plv8 to version 3.1.6

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue that would cause a logical replication slot to transiently error out in the presence of aborted subtransactions and DDL.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

High priority enhancements

• Improved the index scan query performance by skipping unnecessary B-tree page reads when a composite index is used with large data sets

• Fixed an issue with index scan queries that, in rare cases, could lead to database instance restarts

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue that could result in read replica lag due to stale metadata

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39418

  • CVE-2023-39417

High priority enhancements

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads

• Fixed an issue which can cause vacuum operations to become blocked after the restart of an Aurora replica

• Fixed an issue that would cause high CPU usage and prevent new connections

General enhancements

• Introduced diagnostics for the transient metadata used for I/O

General enhancements

• Fixed an issue with the calculation of the AuroraReplicaLag metric

• Fixed a bug which can cause unavailability during ZDP

• Fixed an issue that prevented reclaiming storage on transaction commits

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase

• Added Aurora Serverless v2 scaling enhancements

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters (GUCs), customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms

  • aws_lambda.request_timeout_ms

• Fixed multiple issues which can cause Aurora replicas with the improved read availability feature to restart when reconnecting with the writer instance

• Fixed an issue preventing a survivable reader reconnect

General enhancements

• Fixed an error when loading the test_decoding plugin in pg_create_logical_replication_slot

• Fixed an issue that causes logical replication to fail when using write-through cache

• Updated the Oracle client used by the oracle_fdw extension to version 21.9.0.0.0

New features

• Introduced a new Query Plan Management (QPM) plan hash calculation for multi-schema support. If users want to use QPM in multi-schema environments, they can set the apg_plan_mgmt.plan_hash version to 2 and call apg_plan_mgmt.validate_plans ('update_plan_hash').

• Logical replication enhancements to improve memory and CPU usage during the processing of large transactions.

• The CloudWatch metric ReplicationSlotDiskUsage now tracks logical replication specific storage across Aurora storage and local storage.

• Starting with Aurora PostgreSQL versions 15.2 and 14.7, a user needs to be granted the CONNECT privilege on each database to connect even if the user is granted access to the rds_superuser role. Prior to Aurora PostgreSQL versions 15.2 and 14.7, a user was able to connect to any database and system table if the user was granted the rds_superuser role. Previous Aurora PostgreSQL versions are not impacted by this change, and users with access to the rds_superuser role do not require the CONNECT privilege to access databases in their Aurora PostgreSQL cluster.

General enhancements

• Upgraded PROJ support to version 9.1.0

• Upgraded the GDAL library in PostGIS to version 3.5.3

• Upgraded the pg_hint_plan to version 1.5.0

• Added support for the TCN and SEG extensions

• Improved performance of deletes from b-tree and hash indexes on Aurora replicas

• Includes Aurora Serverless v2 scaling enhancements

• Fixed issue in QPM that prevented the enforcement of approved plans when joining partitioned tables

• Improved engine startup time, particularly on large instances with many objects

• The Aurora function aurora_stat_logical_wal_cache() is now visible to all users

• Fixed an issue in QPM that could cause unavailability when enforcing plans from prepared statements

Additional improvements and enhancements

• Updated the following extensions:

  • apg_plan_mgmt to version 2.4

  • hll to version 2.17

  • Oracle_fdw to version 2.5.0

  • orafce to version 4.0.0

  • pg_audit to version 1.7.0

  • pg_cron to version 1.4.2

  • pg_hint_plan to version 1.5.0

  • pg_logical to version 2.4.2

  • pg_repack to version 1.4.8

  • pg_stat_statements to version 1.10

  • pg_trgm to version 1.4

  • pgrouting to version 3.4.1

  • plv8 to version 3.1.4

  • PostGIS to version 3.3.2

  • rds_activity_stream to version 1.6

  • SEG to version 1.0

  • TCN to version 1.0

  • tds_fdw to version 2.0.3

  • wal2json to version 2.5

General enhancements

• Fixed a performance degradation issue in PLV8 extension.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue where pg_stat_statements can block minor version upgrade during ZDP.

• Fixed an issue where a logical replication slot would no longer emit changes due to an overly strict data consistency check.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

New features

• Amazon Bedrock integration – By using the Amazon Aurora machine learning extension with your Aurora PostgreSQLDB cluster, you can now use Amazon Bedrock foundational AI models.

• Using Active Directory security groups for Aurora PostgreSQL access control – Add group role authentication support using Amazon Directory Service for Microsoft Active Directory with the new pg_ad_mapping extension.

• Delegated Extension Support – This feature allows delegating extension management to lower privileged user with the new rds_extension role.

• Added support for aurora_compute_plan_id parameter which is turned on by default in an Aurora PostgreSQL DB Cluster and DB Parameter Group. For more information, see Monitoring query execution plans for Aurora PostgreSQL.

• Query Plan Management (QPM) enhancements:

  • Plan outlines will be updated to the latest format version as part of the update_plan_hash action for apg_plan_mgmt.validate_plans().

  • Support was added for parallel append enforcement as a part of parallel query enforcement.

• Added support for the HypoPG extension at version 1.4.0.

• Added support for the h3-pg extension and the h3-postgis extension at version 4.1.3.

High priority enhancements

• Fixed an issue which may cause a reboot when logically replicating changes in the presence of concurrently-running DDL or canceled sub-transactions

• Fixed an issue which may cause an Aurora replica to reboot when reading a page which was modified during WAL replay

• Fixed an issue where if a specific volume metadata is invalid on a source cluster, it will remain invalid on a cloned cluster. Since the clone cluster uses a new volume, the metadata will now be recreated.

• Fixed a bug that may cause an engine crash during zero-downtime patching (ZDP)

• Introduced a new parameter, rds.enable_memory_management, which is used to enable and disable the improved memory management feature.

• Improved index scan query performance by skipping unnecessary B-tree page reads when a composite index is used with large data sets.

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General enhancements

• Fixed an issue which may cause an Aurora replica to reboot while reconnecting with the writer DB instance.

• Added support for the rdkit.morgan_fp_size parameter

• rds-superuser can now run the pg_stat_reset_slru function

• Fixed an issue where MultiXact SLRU accesses were not credited to the correct pg_stat_slru category.

• Fixed an issue which may cause unused WAL segements to not be properly removed

• Fixed an issue where pglogical does not correctly pass-through replication origin data when using the binary output format

• rds_superuser can now execute ALTER COLLATION to refresh the collation version of a locale in the catalog.

• Fixed a crash in dblink and postgres_fdw extensions due to invalid connections

• Fixed an issue where the aws_s3 extension can import HTTP error responses into the table

• Fixed an issue which may cause an Aurora Replica instance with Optimized Reads to reboot while reconnecting with the writer DB instance.

• Fixed an issue which may cause an Aurora replica with Optimized Reads to reboot while caching a page to tiered cache.

• Record the version of the Amazon independent default collation library version in pg_collation catalog.

Additional improvements and enhancements

• Updated the following extensions:

  • mysql_fdw to version 2.9.1

  • Oracle_fdw to version 2.6.0

  • Orafce to version 4.6.0

  • pg_cron to version 1.6.0

  • pg_proctab to version 0.0.10

  • pg_tle to version 1.2.0

  • plv8 to version 3.1.8

  • PostGIS to version 3.4.0

  • prefix to version 1.2.10

  • RDKit to version 4.4.0 (Release_2023_09_1)

General enhancements

• Fixed a performance degradation issue in PLV8 extension.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue where pg_stat_statements can block minor version upgrade during ZDP.

• Fixed an issue where a logical replication slot would no longer emit changes due to an overly strict data consistency check.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

High priority enhancements

• Fixed an issue which may cause a reboot when logically replicating changes in the presence of concurrent canceled subtransactions and DDL

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

High priority enhancements

• Improved the index scan query performance by skipping unnecessary B-tree page reads when a composite index is used with large data sets

• Fixed an issue with index scan queries that, in rare cases, could lead to database instance restarts

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

New features

• Added support for mysql_fdw version 2.9.0

• Added support in the aws_s3 extension for exporting to an S3 bucket encrypted with a customer managed KMS key

• Improved the availability of Aurora replicas in the global DB secondary clusters

• Added support for query plan capture on Aurora replicas

• Added support for query plan enforcement with materialize nodes

• Added support for query plan enforcement with parallel query operators

• Allowed query plans under a given cost threshold to not be captured

High priority enhancements

• Included optimizations to improve the time to scale up in Aurora Serverless instances

General enhancements

• Fixed an issue in the aws_s3 extension where the number of rows exported is incorrectly reported when the total number exceeds 2 billion

• Provided options to configure timeouts in the aws_s3 extension. By setting the following parameters (GUCs), customers will now be able to change the timeout thresholds for imports from S3:

  • aws_s3.curlopt_low_speed_limit

  • aws_s3.curlopt_low_speed_time

• Prevented instance creation failure in some edge cases

• Improved the performance of replay of commit transaction operations on Aurora replicas

• Fixed an issue where, in rare cases, an import from the aws_s3 extension fails to complete

• Updated the GEOS library for PostGIS to version 3.12.0

• Improved Aurora Serverless v2 database memory scaling which reduces the overall database instance scale time

• Added the WAIT_EVENT_Aurora_CLUSTER_CACHE_MANAGER_SENDER wait event to denote wait times in the cluster cache manager sender

• Added the WAIT_EVENT_Aurora_SERVERLESS_MONITORING_MAIN wait event to denote wait times in Aurora Serverless resource monitoring

• Improved the handling of invalid non-persisted metadata during reads from storage on read replicas

• Fixed an issue where the database may crash during the start of a logical replication slot

• Increased the limit for pg_cron cron.max_running_jobs parameter from 100 to 1000

• The pgAudit pgaudit.log_statement parameter is now modifiable

• Introduced diagnostics for transient metadata used for I/O

• Fixed a bug in CREATE TABLE command to handle table name starting with '#' correctly

Additional improvements and enhancements

• Updated the following extensions:

  • orafce to version 4.3.0

  • pg_logical to version 2.4.3

  • pg_tle to version 1.1.1

  • pgvector to version 0.5.0

  • PostGIS to version 3.3.3

  • RDKit to version 4.3

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue that would cause a logical replication slot to transiently error out in the presence of aborted subtransactions and DDL.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

High priority enhancements

• Improved the index scan query performance by skipping unnecessary B-tree page reads when a composite index is used with large data sets

• Fixed an issue with index scan queries that, in rare cases, could lead to database instance restarts

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue that could result in read replica lag due to stale metadata

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

High priority stability enhancements

• Backported a fix for the following PostgreSQL community security issue:

  • CVE-2023-39417

High priority enhancements

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads

• Fixed an issue which can cause vacuum operations to become blocked after the restart of an Aurora replica

• Fixed an issue that would cause a crash when executing the COPY FROM command

• Fixed an issue that would cause high CPU usage and prevent new connections

• Fixed an issue where UPDATE and DELETE from a table with foreign key could fail unexpectedly with "ERROR: 40001: could not serialize access due to concurrent update when using Serializable snapshot"

General enhancements

• Introduced diagnostics for the transient metadata used for I/O

• Fixed an issue that prevented the enablement of improved memory management in certain scenarios in Aurora PostgreSQL 15.3

New features

• This release contains memory management improvements which increase database stability and availability by proactively preventing issues caused by insufficient memory. For more information, see Improved memory management in Aurora PostgreSQL.

• Added support for pgvector extension version 0.4.1

High priority enhancements

• Fixed an issue with the subtransaction metadata handling when performing a survivable reader reconnect

• Fixed an issue during ZDP which is related to the extension environment variables

• Addressed a transient error during logical replication that caused a process to incorrectly calculate that it had encountered an unexpected page

• Fixed an issue which causes a period of unavailability due to a partially created replication origin state file

General enhancements

• Addressed an issue where the computing query identifier displayed a warning, "WARNING: unrecognized node type: 378"

• Addressed an issue that caused the initial data sync of a relation to become blocked due to the premature removal of the logical replication slot on the publisher

• Added a new function, aurora_stat_memctx_usage(), to show backend memory use breakdown at a Postgres memory context level

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters (GUCs), customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms

  • aws_lambda.request_timeout_ms

• Fixed an issue with the calculation of the AuroraReplicaLag metric

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots

• Further reduced the database downtime during ZDP

• Fixed a bug which can cause unavailability during ZDP

• Fixed an issue which caused pg_ls_waldir() to return "ERROR: could not stat file"

• Added support for TLS 1.3 with ciphers TLS_AES_128_GCM_SHA256 and TLS_AES_256_GCM_SHA384

• Addressed an issue that blocked a major version upgrade on the Aurora replica of an RDS for PostgreSQL DB instance

• Fixed an issue that could prevent scaling in Aurora Serverless v2 instances

• Fixed an issue in logical replication which, in rare cases, can cause a period of unavailability due to the incorrect subtransaction metadata

• Fixed an issue in the pg_vector extension where, in rare cases, infinite or NAN values caused a crash during the index creation

• Upgraded GEOS to version 3.11.2

• Upgraded pg_cron to version 1.5

• Upgraded pg_partman to version 4.7.3

• Upgraded pg_tle to version 1.0.3

• Upgraded plv8 to version 3.1.6

• Upgraded tds_fdw to 2.0.3

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue that would cause a logical replication slot to transiently error out in the presence of aborted subtransactions and DDL.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

High priority enhancements

• Improved the index scan query performance by skipping unnecessary B-tree page reads when a composite index is used with large data sets

• Fixed an issue with index scan queries that, in rare cases, could lead to database instance restarts

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue that could result in read replica lag due to stale metadata

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

High priority stability enhancements

• Backported a fix for the following PostgreSQL community security issue:

  • CVE-2023-39417

  • CVE-2023-2454

High priority enhancements

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads

• Fixed an issue which can cause vacuum operations to become blocked after the restart of an Aurora replica

• Fixed an issue that would cause high CPU usage and prevent new connections

General enhancements

• Introduced diagnostics for the transient metadata used for I/O

General enhancements

• Fixed an issue with the calculation of the AuroraReplicaLag metric

• Fixed a bug which can cause unavailability during ZDP

• Fixed an issue that prevented reclaiming storage on transaction commits

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase

• Added Aurora Serverless v2 scaling enhancements

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters (GUCs), customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms

  • aws_lambda.request_timeout_ms

• Fixed multiple issues which can cause Aurora replicas with the improved read availability feature to restart when reconnecting with the writer instance

• Fixed an issue preventing a survivable reader reconnect

General enhancements

• Fixed an error when loading the test_decoding plugin in pg_create_logical_replication_slot

• Fixed an issue that causes logical replication to fail when using write-through cache

• Updated the Oracle client used by the oracle_fdw extension to version 21.9.0.0.0

New features

• Introduced a new QPM plan hash calculation for multi-schema support. If users want to use QPM in multi-schema environments, they can set the apg_plan_mgmt.plan_hash version to 2 and call apg_plan_mgmt.validate_plans('update_plan_hash').

• Logical replication enhancements to improve memory and CPU usage during the processing of large transactions.

• The CloudWatch metric ReplicationSlotDiskUsage now tracks logical replication specific storage across Aurora storage and local storage.

• Starting with Aurora PostgreSQL versions 15.2 and 14.7, a user needs to be granted the CONNECT privilege on each database to connect even if the user is granted access to the rds_superuser role. Prior to Aurora PostgreSQL versions 15.2 and 14.7, a user was able to connect to any database and system table if the user was granted the rds_superuser role. Previous Aurora PostgreSQL versions are not impacted by this change, and users with access to the rds_superuser role do not require the CONNECT privilege to access databases in their Aurora PostgreSQL cluster.

High priority stability enhancements

• Fixed an issue where the commit latency metrics weren't updated

General enhancements

• Upgraded PROJ support to version 9.1.0

• Upgraded the GDAL library in PostGIS to version 3.5.3

• Fixed the upgrade paths from pg_hint_plan 1.3x to 1.4

• Added support for the TCN and SEG extensions

• Improved performance of deletes from b-tree and hash indexes on Aurora replicas

• Includes Aurora Serverless v2 scaling enhancements

• Fixed an issue in QPM that prevented the enforcement of approved plans when joining partitioned tables

• Fixed an issue that caused incorrect buffer hit counts in EXPLAIN

• Improved the engine startup time, particularly on large instances with many objects

• The Aurora function aurora_stat_logical_wal_cache() is now visible to all users

• Fixed an issue in QPM that could cause unavailability when enforcing plans from prepared statements

Additional improvements and enhancements

• Updated the following extensions:

  • hll to version 2.17

  • Oracle_fdw to version 2.5.0

  • orafce to version 4.0.0

  • pg_cron to version 1.4.2

  • pg_hint_plan to version 1.4.1

  • pg_logical to version 2.4.2

  • pg_trgm to version 1.4

  • pgrouting to version 3.4.1

  • plv8 to version 3.1.4

  • PostGIS to version 3.3.2

  • SEG to version 1.0

  • TCN to version 1.0

  • wal2json to version 2.5

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

Critical stability enhancements

• Backported a fix for the following PostgreSQL community security issue:

  • CVE-2023-2455

  • CVE-2023-2454

High priority stability enhancements

• Fixed an issue which can cause a database instance to restart while executing IO intensive read workloads

• Fixed an issue that would cause high CPU usage and prevent new connections

General enhancements

• Introduced diagnostics for the transient metadata used for I/O

General enhancements

• Added Aurora Serverless v2 scaling enhancements

• Fixed an issue in pg_cron which can prevent scaling in Aurora Serverless v2

• Fixed an issue with the calculation of the AuroraReplicaLag metric

• Fixed a bug which can cause unavailability during ZDP

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms

  • aws_lambda.request_timeout_ms

Critical stability enhancements

• Backported a fix for the following PostgreSQL community security issue:

  • CVE-2022-41862

General stability enhancements

• Fixed an issue where the approved plans for joins with partitioned tables weren't being enforced

• Fixed an issue in PostGIS where the GDAL data wasn't loading

• Fixed an issue that increased the amount of recovery work during startup if logical replication is enabled

• Fixed an issue with the aws_s3 extension where loading a large number of records can time out

• Fixed an issue that causes logical replication to fail when using write-through cache

Critical stability enhancements

• Fixed a critical stability issue.

High priority stability enhancements

• Fixed an issue where an upgrade fails because the oldest MultiXactId is updated incorrectly

• Fixed an issue that could lead to a brief period of unavailability

General stability enhancements

• Fixed an issue that caused DB instance migration failures

• Fixed an issue where the DB fails to start because of an inconsistency in the metadata

• Improved the error handling and diagnosability

• Upgraded the RDKit extension to version 4.2

• Upgraded the GDAL library to version 3.4.3

• Fixed an issue where the cluster cache management process doesn't shutdown gracefully

• Fixed an issue that can cause certain processes to linger in an inconsistent state during a clean shutdown

• Fixed an issue with the pg_repack extension

• Improved the collation library, glibc, handling with a new independent default collation library

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39417

  • CVE-2023-2455

  • CVE-2023-2454

  • CVE-2022-41862

High priority enhancements

• Fixed an issue which blocked vacuum operations after the restart of an Aurora replica

• Fixed an issue that would cause high CPU usage and prevent new connections

General stability enhancements

• Fixed an issue which causes the stats collector process to repeatedly restart

• Improved the scale times for Aurora Serverless v2

• Fix a bug which can cause unavailability during ZDP

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an S3 bucket with a name containing dots

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms

  • aws_lambda.request_timeout_ms

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads

• Fixed an issue that causes logical replication to fail when using write-through cache

General stability enhancements

• Fixed an issue where the approved plans for joins with partitioned tables weren't being enforced

• Fixed an issue that could cause the unavailability of query plan management (QPM)

• Fixed an issue that increased the amount of recovery work during startup if logical replication is enabled

• Fixed an issue with the aws_s3 extension where loading a large number of records can time out

• Fixed an issue with the pg_cron parallel running of tasks

General stability enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance

• Fixed an issue where the engine experiences stability issues during database minor and patch release upgrades

• Fixed an issue that could cause unavailability during replication

• Fixed an issue that could cause data inconsistency during replication

High priority stability enhancements

• Fixed an Aurora Serverless v2 scaling issue

• Fixed an issue which caused Aurora Serverless v2 shrink failure

General stability enhancements

• Improved buffer cache scavenging when the buffer cache is in duress

• Fixed an issue in database activity streams that leads to high memory consumption

• Fixed an issue where DB instances could restart when applying changes from a logical replication subscription

• Fixed an issue that caused DB instance restarts

• Fixed an issue where a DB instance restarts recursively while generating monitoring metrics during a crash

• Fixed an issue where a DB instance restarted during performance metric collection

• Fixed an issue where an attempt to connect to the database would fail with SSLV3_ALERT_CERTIFICATE_UNKNOWN

• Improved the error reporting in case of an inconsistent B-tree index

• Improved the diagnostic logging around setting invalid hint bits

• Fixed an issue where autovacuum would incorrectly skip tables

• Improved the logical replication prefetching

• Fixed a durability issue in the GIN indexes

• Provided options to configure MultiXact SLRU cache. By setting the following parameters (GUCs), customers will now be able to change the MultiXact SLRU cache sizes:

  • multixact_members_cache_size

  • multixact_offsets_cache_size

• Fixed an issue to detect and cancel stuck major version upgrades

• Fixed an issue in hash join that could lead to increased memory consumption

• Improved the logical replication performance

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable

• Upgraded the GEOS version to 3.10.3

• Updated the PLV8 version to 3.0.0

• Updated the PostGIS extension to version 3.2.3

• Fixed an issue with st_orientedenvelope that caused it to loop with a 1-D input to return 0

• Fixed an issue where the connection to SQL Server using tds_fdw fails

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39417

  • CVE-2023-2455

  • CVE-2023-2454

  • CVE-2022-41862

  • CVE-2022-2625

High priority enhancements

• Fixed an issue which blocked vacuum operations after the restart of an Aurora replica

• Fixed an issue that would cause high CPU usage and prevent new connections

General stability enhancements

• Fixed an issue which causes the stats collector process to repeatedly restart

• Improved the scale times for Aurora Serverless v2

• Fix a bug which can cause unavailability during ZDP

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an S3 bucket with a name containing dots

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms

  • aws_lambda.request_timeout_ms

General stability enhancements

• Fixed an issue where the engine experiences stability issues during database minor and patch release upgrades

• Fixed an issue that could cause unavailability during replication

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable

• Fixed an issue that could cause data inconsistency during replication

High priority stability enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance

High priority stability enhancements

• Fixed an issue where PLV8 crashed during a JavaScript error scenario

• Fixed an issue where PLV8 crashed when trying to acquire a semaphore to execute the next task

• Fixed an issue where scaling an Aurora Serverless v2 instance gets stuck if VACUUM is running

General stability enhancements

• Fixed a bug where Aurora PostgreSQL can't file the relfilenode

• Fixed a database restart issue when a plan gets invaliated but the engine still checks if it is valid

• Fixed a stuck scaling issue when the current scaling event times out

• Upgraded the plv8 extension to version 3.0.0

• Upgraded the PostGIS extension to version 3.2.3

• Fixed an issue where extended query messages might be lost during zero-downtime patching (ZDP) causing the extended query to hang after the ZDP completion

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39417

  • CVE-2023-2455

  • CVE-2023-2454

  • CVE-2022-41862

  • CVE-2022-2625

High priority enhancements

• Fixed an issue which blocked vacuum operations after the restart of an Aurora replica

• Fixed an issue that would cause high CPU usage and prevent new connections

General stability enhancements

• Fixed an issue which causes the stats collector process to repeatedly restart

• Improved the scale times for Aurora Serverless v2

• Fix a bug which can cause unavailability during ZDP

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an S3 bucket with a name containing dots

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms

  • aws_lambda.request_timeout_ms

General stability enhancements

• Fixed an issue where the engine experiences stability issues during database minor and patch release upgrades

• Fixed an issue that could cause unavailability during replication

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable

• Fixed an issue that could cause data inconsistency during replication

High priority stability enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance

High priority stability enhancements

• Fixed a PLV8 issue where the base parameter doesn't get loaded properly into the memory

• Fixed an issue where scaling an Aurora Serverless v2 instance gets stuck if VACUUM is running

General stability enhancements

• Fixed a bug where Aurora PostgreSQL can't file the relfilenode

• Fixed a database restart issue when a plan gets invaliated but the engine still checks if it is valid

• Fixed a stuck scaling issue when the current scaling event times out

• Upgraded the PostGIS extension to version 3.1.7

• Fixed an issue where extended query messages might be lost during zero-downtime patching (ZDP) causing the extended query to hang after the ZDP completion

Critical stability enhancements

• Fixed an issue that could cause periods of unavailability during a storage node restart

High priority stability enhancements

• Fixed an error handling issue related to out-of-memory conditions which could result in brief periods of unavailability

• Fixed an issue when the connection to SQL Server fails using the TDS_FDW extension to query a foreign table

• Fixed an issue that caused connections using the provided root certificate to fail

• Improved the diagnostic and supportability information in case of inconsistent B-tree index entries

New features

• Supports SCRAM password encryption method. For more information, see Using SCRAM for PostgreSQL password encryption.

Additional improvements and enhancements

• Contains all of the fixes, features, and improvements present in Aurora PostgreSQL 13.7.

• Backported the following bug fix from the PostgreSQL 14.4 release: Reverted changes to CONCURRENTLY that "sped up" Xmin advance to prevent Index Corruption with the CREATE INDEX CONCURRENTLY / REINDEX CONCURRENTLY commands.

• This release supports lo extension version 1.1.

• This release supports old_snapshot extension version 1.0.

• This release supports EBCDIC collations for the mainframe modernization efforts. For more information, see Aurora PostgreSQL collations for EBCDIC and other mainframe migrations in the Amazon Aurora User Guide.

• Updated the following extensions:

  • amcheck to version 1.3

  • btree_gist to version 1.6

  • cube to version 1.5

  • hll to version 2.16

  • hstore to version 1.8

  • intarray to version 1.5

  • log_fdw to version 1.3

  • oracle_fdw to version 2.4.0

  • pg_hint_plan to version 1.4

  • pg_partman to version 4.6.0

  • pg_repack to version 1.4.7

  • pg_stat_statements to version 1.9

  • pg_trgm to version 1.6

  • pgaudit to version 1.6.1

  • pgrouting to version 3.2.0

  • pgtap to version 1.2.0

  • postgres_fdw to version 1.1

General enhancements

• Fixed a performance degradation issue in PLV8 extension.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue where pg_stat_statements can block minor version upgrade during ZDP.

• Fixed an issue where a logical replication slot would no longer emit changes due to an overly strict data consistency check.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

New features

• Amazon Bedrock integration – By using the Amazon Aurora machine learning extension with your Aurora PostgreSQLDB cluster, you can now use Amazon Bedrock foundational AI models.

• Delegated Extension Support – This feature allows delegating extension management to lower privileged user with the new rds_extension role.

• Query Plan Management (QPM) enhancements:

  • Plan outlines will be updated to the latest format version as part of the update_plan_hash action for apg_plan_mgmt.validate_plans().

  • Support was added for parallel append enforcement as a part of parallel query enforcement.

• Added support for the HypoPG extension at version 1.4.0.

• Added support for the h3-pg extension and the h3-postgis extension at version 4.1.3.

High priority enhancements

• Fixed an issue which may cause an Aurora replica to reboot when reading a page which was modified during WAL replay

• Fixed an issue where if a specific volume metadata is invalid on a source cluster, it will remain invalid on a cloned cluster. Since the clone cluster uses a new volume, the metadata will now be recreated.

• Fixed an issue which could, in rare cases, lead to an engine unavailable condition following a minor or patch version upgrade

• Fixed a bug that may cause an engine crash during zero-downtime patching (ZDP)

• Introduced a new parameter, rds.enable_memory_management, which is used to enable and disable the improved memory management feature.

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General enhancements

• Fixed an issue which may cause an Aurora replica to reboot while reconnecting with the writer DB instance.

• Added support for the rdkit.morgan_fp_size parameter

• rds-superuser can now run the pg_stat_reset_slru function

• Fixed an issue where MultiXact SLRU accesses were not credited to the correct pg_stat_slru category.

• Fixed an issue which may cause unused WAL segements to not be properly removed

• Fixed an issue where pglogical does not correctly pass-through replication origin data when using the binary output format

• rds_superuser can now execute ALTER COLLATION to refresh the collation version of a locale in the catalog.

• Fixed a crash in dblink and postgres_fdw extensions due to invalid connections

• Fixed an issue where the aws_s3 extension can import HTTP error responses into the table

• Record the version of the Amazon independent default collation library version in pg_collation catalog.

Additional improvements and enhancements

• Updated the following extensions:

  • mysql_fdw to version 2.9.1

  • Oracle_fdw to version 2.6.0

  • Orafce to version 4.6.0

  • pg_cron to version 1.6.0

  • pg_hint_plan to version 1.3.9

  • pg_proctab to version 0.0.10

  • plv8 to version 3.1.8

  • PostGIS to version 3.4.0

  • prefix to version 1.2.10

  • RDKit to version 4.4.0 (Release_2023_09_1)

General enhancements

• Fixed a performance degradation issue in PLV8 extension.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue where pg_stat_statements can block minor version upgrade during ZDP.

• Fixed an issue where a logical replication slot would no longer emit changes due to an overly strict data consistency check.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

New features

• Added support for mysql_fdw version 2.9.0

• Added support in the aws_s3 extension for exporting to an S3 bucket encrypted with a customer managed KMS key

• Improved the availability of Aurora replicas in the global DB secondary clusters

• Added support for query plan capture on Aurora replicas

• Added support for query plan enforcement with parallel query operators

• Allowed query plans under a given cost threshold to not be captured

High priority enhancements

• Included optimizations to improve the time to scale up in Aurora Serverless instances

General enhancements

• Fixed an issue in the aws_s3 extension where the number of rows exported is incorrectly reported when the total number exceeds 2 billion

• Provided options to configure timeouts in the aws_s3 extension. By setting the following parameters (GUCs), customers will now be able to change the timeout thresholds for imports from S3:

  • aws_s3.curlopt_low_speed_limit

  • aws_s3.curlopt_low_speed_time

• Prevented instance creation failure in some edge cases

• Improved the performance of replay of commit transaction operations on Aurora replicas

• Fixed an issue where, in rare cases, an import from the aws_s3 extension fails to complete

• Updated the GEOS library for PostGIS to version 3.12.0

• Improved Aurora Serverless v2 database memory scaling which reduces the overall database instance scale time

• Added the WAIT_EVENT_Aurora_CLUSTER_CACHE_MANAGER_SENDER wait event to denote wait times in the cluster cache manager sender

• Added the WAIT_EVENT_Aurora_SERVERLESS_MONITORING_MAIN wait event to denote wait times in Aurora Serverless resource monitoring

• Fixed an issue where the database may crash during the start of a logical replication slot

• Increased the limit for pg_cron cron.max_running_jobs parameter from 100 to 1000

• Fixed a bug in CREATE TABLE command to handle table name starting with '#' correctly.

Additional improvements and enhancements

• Updated the following extensions:

  • orafce to version 4.3.0

  • pg_logical to version 2.4.3

  • pgvector to version 0.5.0

  • PostGIS to version 3.3.3

  • RDKit to version 4.3

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue that would cause a logical replication slot to transiently error out in the presence of aborted subtransactions and DDL.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue that could result in read replica lag due to stale metadata

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

High priority stability enhancements

• Backported a fix for the following PostgreSQL community security issue:

  • CVE-2023-39417

High priority enhancements

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads.

• Fixed an issue which can cause vacuum operations to become blocked after the restart of an Aurora replica.

• Fixed an issue that would cause a crash when executing the COPY FROM command.

• Fixed an issue that would cause high CPU usage and prevent new connections.

• Fixed an issue where UPDATE and DELETE from a table with foreign key could fail unexpectedly with "ERROR: 40001: could not serialize access due to concurrent update when using Serializable snapshot".

General enhancements

• Introduced diagnostics for the transient metadata used for I/O.

• Fixed an issue that prevented the enablement of improved memory management in certain scenarios in Aurora PostgreSQL 15.3.

New features

• This release contains memory management improvements which increase database stability and availability by proactively preventing issues caused by insufficient memory. For more information, see Improved memory management in Aurora PostgreSQL.

• Added support for the pgvector extension version 0.4.1.

High priority enhancements

• Fixed an issue with the subtransaction metadata handling when performing a survivable reader reconnect.

• Fixed an issue during ZDP which is related to the extension environment variables.

• Addressed a transient error during logical replication that caused a process to incorrectly calculate that it had encountered an unexpected page.

• Fixed an issue which causes a period of unavailability due to a partially created replication origin state file.

General enhancements

• Added a new function, aurora_stat_memctx_usage(), to show backend memory use breakdown at a Postgres memory context level.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters (GUCs), customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

• Fixed an issue with the calculation of the AuroraReplicaLag metric.

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots.

• Further reduced the database downtime during ZDP.

• Fixed a bug which can cause unavailability during ZDP.

• Fixed an issue which caused pg_ls_waldir() to return "ERROR: could not stat file".

• Added support for TLS 1.3 with ciphers TLS_AES_128_GCM_SHA256 and TLS_AES_256_GCM_SHA384.

• Addressed an issue that blocked a major version upgrade on the Aurora replica of an RDS for PostgreSQL DB instance.

• Fixed an issue that could prevent scaling in Aurora Serverless v2 instances.

• Fixed an issue in the pg_vector extension where, in rare cases, infinite or NAN values caused a crash during the index creation.

• Fixed an issue to improve the performance.

• Upgraded GEOS to version 3.11.2.

• Upgraded pg_cron to version 1.5.

• Upgraded pg_partman to version 4.7.3.

• Upgraded plv8 to version 3.1.6.

• Upgraded tds_fdw to 2.0.3.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue that would cause a logical replication slot to transiently error out in the presence of aborted subtransactions and DDL.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue that could result in read replica lag due to stale metadata

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

High priority stability enhancements

• Backported a fix for the following PostgreSQL community security issue:

  • CVE-2023-39417

High priority enhancements

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads.

• Fixed an issue which can cause vacuum operations to become blocked after the restart of an Aurora replica.

• Fixed an issue that would cause high CPU usage and prevent new connections.

General enhancements

• Introduced diagnostics for the transient metadata used for I/O.

General enhancements

• Fixed an issue with the calculation of the AuroraReplicaLag metric.

• Fixed a bug which can cause unavailability during ZDP.

• Fixed an issue that prevented reclaiming storage on transaction commits.

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase.

• Added Aurora Serverless v2 scaling enhancements.

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters (GUCs), customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

• Fixed multiple issues which can cause Aurora replicas with the improved read availability feature to restart when reconnecting with the writer instance.

• Fixed an issue preventing a survivable reader reconnect.

General enhancements

• Fixed an error when loading the test_decoding plugin in pg_create_logical_replication_slot.

• Fixed an issue that causes logical replication to fail when using write-through cache.

• Updated the Oracle client used by the oracle_fdw extension to version 21.9.0.0.0.

New features

• Introduced a new QPM plan hash calculation for multi-schema support. If users want to use QPM in multi-schema environments, they can set the apg_plan_mgmt.plan_hash version to 2 and call apg_plan_mgmt.validate_plans('update_plan_hash').

General enhancements

• Upgraded PROJ support to version 9.1.0.

• Upgraded the GDAL library in PostGIS to version 3.5.3.

• Added support for the TCN and SEG extensions.

• Improved performance of deletes from b-tree and hash indexes on Aurora replicas.

• Includes Aurora Serverless v2 scaling enhancements.

• Fixed an issue in QPM that prevented the enforcement of approved plans when joining partitioned tables.

• Fixed an issue that caused incorrect buffer hit counts in EXPLAIN.

• Improved the engine startup time, particularly on large instances with many objects.

• The Aurora function aurora_stat_logical_wal_cache() is now visible to all users.

• Fixed an issue in QPM that could cause unavailability when enforcing plans from prepared statements.

Additional improvements and enhancements

• Updated the following extensions:

  • hll to version 2.17

  • Oracle_fdw to version 2.5.0

  • orafce to version 4.0.0

  • pg_cron to version 1.4.2

  • pg_hint_plan to version 1.3.8

  • pg_logical to version 2.4.2

  • pg_trgm to version 1.4

  • pgrouting to version 3.4.1

  • PostGIS to version 3.3.2

  • SEG to version 1.0

  • TCN to version 1.0

  • wal2json to version 2.5

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

Critical stability enhancements

• Backported a fix for the following PostgreSQl community security issue:

  • CVE-2023-2455

  • CVE-2023-2454

High priority stability enhancements

• Fixed an issue which can cause a database instance to restart while executing IO intensive read workloads.

• Fixed an issue that would cause high CPU usage and prevent new connections.

General enhancements

• Introduced diagnostics for the transient metadata used for I/O.

General enhancements

• Added Aurora Serverless v2 scaling enhancements.

• Fixed an issue in pg_cron which can prevent scaling in Aurora Serverless v2.

• Fixed an issue with the calculation of the AuroraReplicaLag metric.

• Fixed a bug which can cause unavailability during ZDP.

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase.

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

Critical stability enhancements

• Backported a fix for the following PostgreSQL community security issue:

  • CVE-2022-41862

General stability enhancements

• Fixed an issue where the approved plans for joins with partitioned tables weren't being enforced.

• Fixed an issue in PostGIS where the GDAL data wasn't loading.

• Fixed an issue that increased the amount of recovery work during startup if logical replication is enabled.

• Fixed an issue with the aws_s3 extension where loading a large number of records can time out.

• Fixed an issue that causes logical replication to fail when using write-through cache

High priority stability enhancements

• Fixed an issue where an upgrade fails because the oldest MultiXactId is updated incorrectly.

• Fixed an issue where the commit latency metrics weren't updated.

• Fixed an issue that could lead to a brief period of unavailability.

General stability enhancements

• Fixed an issue that caused DB instance migration failures.

• Fixed an issue where the DB fails to start because of an inconsistency in the metadata.

• Improved the error handling and diagnosability.

• Upgraded the RDKit extension to version 4.2.

• Upgraded the GDAL library to version 3.4.3.

• Fixed an issue where the cluster cache management process doesn't shutdown gracefully.

• Fixed an issue that can cause certain processes to linger in an inconsistent state during a clean shutdown.

• Fixed an issue with the pg_repack extension.

• Improved the collation library (glibc) handling with a new independent default collation library.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39417

  • CVE-2023-2455

  • CVE-2023-2454

  • CVE-2022-41862

High priority enhancements

• Fixed an issue which blocked vacuum operations after the restart of an Aurora replica.

• Fixed an issue that would cause high CPU usage and prevent new connections.

General stability enhancements

• Fixed an issue which causes the stats collector process to repeatedly restart.

• Improved the scale times for Aurora Serverless v2.

• Fix a bug which can cause unavailability during ZDP.

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase.

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an S3 bucket with a name containing dots.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads.

• Fixed an issue that causes logical replication to fail when using write-through cache

General stability enhancements

• Fixed an issue where the approved plans for joins with partitioned tables weren't being enforced.

• Fixed an issue that increased the amount of recovery work during startup if logical replication is enabled.

• Fixed an issue with the aws_s3 extension where loading a large number of records can time out.

• Fixed an issue with the pg_cron parallel running of tasks.

General stability enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance.

• Fixed an issue where the engine experiences stability issues during database minor and patch release upgrades.

• Fixed an issue that could cause data inconsistency during replication.

High priority stability enhancements

• Fixed an Aurora Serverless v2 scaling issue.

• Fixed an issue which caused Aurora Serverless v2 shrink failure.

General stability enhancements

• Improved buffer cache scavenging when the buffer cache is in duress.

• Fixed an issue in Database Activity Streams that leads to high memory consumption.

• Fixed an issue that caused DB instance restarts.

• Fixed an issue where a DB instance restarts recursively while generating monitoring metrics during a crash.

• Fixed an issue where a DB instance restarted during performance metric collection.

• Fixed an issue where an attempt to connect to the database would fail with SSLV3_ALERT_CERTIFICATE_UNKNOWN.

• Improved the error reporting in case of an inconsistent B-tree index.

• Improved the diagnostic logging around setting invalid hint bits.

• Fixed an issue where autovacuum would incorrectly skip tables.

• Improved the logical replication prefetching.

• Fixed a durability issue in the GIN indexes.

• Provided options to configure MultiXact SLRU cache. By setting the following parameters (GUCs), customers will now be able to change the MultiXact SLRU cache sizes:

  • multixact_members_cache_size

  • multixact_offsets_cache_size

• Fixed an issue to detect and cancel stuck major version upgrades.

• Fixed an issue in hash join that could lead to increased memory consumption.

• Improved the logical replication performance.

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

• Upgraded the GEOS version to 3.10.3.

• Updated the PLV8 version to 3.0.0.

• Updated the PostGIS extension to version 3.2.3.

• Fixed an issue with st_orientedenvelope that caused it to loop with a 1-D input to return 0.

• Fixed an issue where the connection to SQL Server using tds_fdw fails.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39417

  • CVE-2023-2455

  • CVE-2023-2454

  • CVE-2022-41862

  • CVE-2022-2625

High priority enhancements

• Fixed an issue which blocked vacuum operations after the restart of an Aurora replica.

• Fixed an issue that would cause high CPU usage and prevent new connections.

General stability enhancements

• Fixed an issue which causes the stats collector process to repeatedly restart.

• Improved the scale times for Aurora Serverless v2.

• Fix a bug which can cause unavailability during ZDP.

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase.

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an S3 bucket with a name containing dots.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

General stability enhancements

• Fixed an issue where the engine experiences stability issues during database minor and patch release upgrades.

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

• Fixed an issue that could cause data inconsistency during replication.

High priority stability enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance.

High priority stability enhancements

• Fixed a PLV8 issue where the base parameter doesn't get loaded properly into the memory.

• Fixed an issue where scaling an Aurora Serverless v2 instance gets stuck if VACUUM is running.

General stability enhancements

• Fixed a bug where Aurora PostgreSQL can't file the relfilenode.

• Fixed a database restart issue when a plan gets invaliated but the engine still checks if it is valid.

• Fixed a stuck scaling issue when the current scaling events time out.

• Upgraded the PostGIS extension to version 3.1.7.

• Fixed an issue where extended query messages might be lost during zero-downtime patching (ZDP) causing the extended query to hang after the ZDP completion.

Critical stability enhancements

• Fixed an issue that could cause periods of unavailability during a storage node restart.

High priority stability enhancements

• Fixed an error handling issue related to out-of-memory conditions which could result in brief periods of unavailability.

• Fixed an issue when the connection to SQL Server fails using the TDS_FDW extension to query a foreign table.

• Fixed an issue that caused connections using the provided root certificate to fail.

• Improved the diagnostic and supportability information in case of inconsistent B-tree index entries.

New features

• Added support for the large object module (extension). For more information, see Managing large objects with the lo module.

• Added support for zero-downtime patching (ZDP) for minor version upgrades and patches. For more information, see Minor release upgrades and zero-downtime patching in the Amazon Aurora User Guide.

Critical updates

• Fixed a replay crash due to an LSN mismatch

• Fixed the aws_s3 extension to prevent invalid region injection

High stability updates

• Fixed multiple issues related to out-of-memory conditions which could result in brief periods of unavailability

• Fixed an Aurora Serverless v2 scaling issue.

General enhancements

• Fixed a lock contention crash during an Aurora Serverless v1 scaling event.

• Fixed an issue where logical replication becomes stuck after a restart.

• Fixed multiple issues that could lead to brief periods of unavailability.

• Fixed a crash in pg_cron due to a task still running but being unscheduled.

• Fixed, during redo, an invalid page hit on the Generic Redo for GENERIC_XLOG_FULL_PAGE_DATA. This happens due to a timing hole between generating the log record and then writing the metadata for the record on the RW node and the RO node replays between those operations.

• Improved the query performance by supporting parallel workers.

• Upgraded the plugin wal2json version to 2.4.

• Upgraded the pglogical extension to version 2.4.1.

General enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance.

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

High priority enhancements

• Fixed an issue where Amazon Aurora Serverless v2 scaling may get blocked if VACUUM is running.

• Fixed an issue where Amazon Aurora Serverless v2 scaling may get blocked on Aurora replicas.

General enhancements

• Improved the diagnostic and supportability information in case of inconsistent B-tree index entries.

• Updated the PostGIS extension to version 3.1.7.

Security enhancements

• Backpatched the PostgreSQL community fix for CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation". For more information, see CVE-2022-1552.

Critical enhancements

• Fixed an issue during a storage node restart that could result in periods of unavailability.

High priority stability enhancements

• Fixed an error handling issue related to out-of-memory conditions that could result in brief periods of unavailability.

• Fixed an issue related to the existence of duplicate relation files that could result in periods of unavailability.

• Fixed a defect where the validation of cached plans may lead to a database restart when the plan was previously invalidated.

Security enhancements

• Backpatched the PostgreSQL community fix for CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation". For more information, see CVE-2022-1552.

High priority stability updates

• Fixed an issue that can lead to a blocked scale operation when a COPY command is in progress in Amazon Aurora Serverless v2.

• Fixed an issue that can cause a restart of the database when dropping or truncating tables in Amazon Aurora Serverless v2.

• Fixed an issue in the apg_prewarm extension that can lead to a blocked scale operation in Amazon Aurora Serverless v2.

• Fixed an issue in the dynamic shared memory allocation that can lead to a blocked scale operation in Amazon Aurora Serverless v2.

• Fixed an issue that can cause a restart of the postmaster process in Amazon Aurora Serverless v2.

• Fixed an issue where a minor version ugprade may get blocked when there is a SQL view that refers to the checksum() function in Babelfish for Aurora PostgreSQL.

• Fixed an issue in apg_plan_mgmt that can cause a restart when Query Plan Management (QPM) is enabled.

High priority stability enhancements

• Fixed an issue that causes upgrades to fail when Babelfish for Aurora PostgreSQL is enabled.

• Fixed an issue that causes scaling in Aurora Serverless v2 to fail.

General enhancements

• Fixed an issue that could cause unavailability due to improper locking of shared memory.

High priority stability enhancements

• Fixed an issue that could cause incorrect WriteIOPS reporting in the Amazon console.

• Fixed an issue that could cause unavailability after removal of a read node from a cluster.

General enhancements

• Fixed an issue that could cause an engine restart during periods of low free memory.

New features

• Added support for the tds_fdw extension version 2.0.2.

High priority stability enhancements

• Fixed multiple issues that may result in unavailability of a read node.

• Fixed an issue that may result in a read node being unable to replay WAL requiring the replication slot to be dropped and resynchronized.

• Fixed an issue that could cause excess storage use due to files not being properly closed.

General enhancements

• Fixed a small memory leak on read nodes when commit_ts is set.

• Fixed an issue that caused Performance Insights to show "Unknown wait event".

• Fixed an issue that could cause an import from Amazon S3 to fail when using the aws_s3 extension

• Fixed multiple issues that could result in periods of unavailability when using apg_plan_mgmt

• Fixed multiple issues that could result in periods of unavailability when QPM is enabled

General enhancements

• Fixed an issue which causes the stats collector process to repeatedly restart.

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase.

General enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance.

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

General enhancements

• Improved the diagnostic and supportability information in case of inconsistent B-tree index entries.

• Updated the PostGIS extension to version 3.1.7.

Security enhancements

• Backpatched the PostgreSQL community fix for CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation". For more information, see CVE-2022-1552.

Critical enhancements

• Fixed an issue during a storage node restart that could result in periods of unavailability.

High stability enhancements

• Fixed an error handling issue related to out-of-memory conditions that could result in brief periods of unavailability.

• Fixed an issue related to the existence of duplicate relation files that could result in periods of unavailability.

• Fixed an issue that could cause excess storage use due to files not being properly closed.

• Fixed an issue that can cause a restart of the postmaster process in Amazon Aurora Serverless v2.

• Fixed an issue that caused Performance Insights to show "Unknown wait event".

Security enhancements

• Additional modifications to the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

General enhancements

• Fixed a bug that could cause an engine restart during periods of low free memory.

Security enhancements

• Updated the PostGIS extension from version 3.1.4 to 3.1.5. This update contains a PostGIS fix for the vulnerability addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the ip4r extension to mitigate a security issue during create extension. The issue was originally disclosed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the pg_bigm extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

High priority stability enhancements

• Fixed a bug where logical replication may hang resulting in the replay falling behind on the read node. The instance may eventually restart.

Additional improvements and enhancements

• Added the Buffers: shared hit metric to the Explain output.

• Fixed a buffer cache bug that could cause brief periods of unavailability.

• Fixed a bug in the apg_plan_mgmt extension where an index based plan was not being enforced.

• Fixed a bug in the pg_logical extension that could cause brief periods of unavailability due to improper handling of NULL arguments.

• Fixed a bug that could cause brief periods of unavailability due to reading uninitialized pages.

• Fixed an issue where orphaned files caused major version upgrades to fail.

• Fixed incorrect Aurora Storage Daemon log write metrics.

• Fixed multiple bugs that could result in WAL replay falling behind and eventually causing the reader instances to restart.

• Improved the Aurora buffer cache page validation on reads.

• Improved the Aurora storage metadata validation.

• The pg_cron extension is updated to 1.4.1

General enhancements

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

General enhancements

• Improved the diagnostic and supportability information in case of inconsistent B-tree index entries.

• Updated the PostGIS extension to version 3.1.7.

Security enhancements

• Backpatched the PostgreSQL community fix for CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation". For more information, see CVE-2022-1552.

General enhancements

• Fixed an error handling issue related to out-of-memory conditions which could result in brief periods of unavailability.

• Fixed an issue that could cause excess storage use due to files not being properly closed.

• Fixed an issue that could cause a restart of the postmaster process in Amazon Aurora Serverless v2.

• Fixed an issue that could cause Performance Insights to display "Unknown wait event".

• Fixed an issue that could result in periods of unavailability due to the existence of duplicate relation files.

Security enhancements

• Additional modifications to the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

General enhancements

• Fixed a buffer cache bug that could cause brief periods of unavailability.

Security enhancements

• Updated the PostGIS extension from version 3.1.4 to 3.1.5. This update contains a PostGIS fix for the vulnerability addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the ip4r extension to mitigate a security issue during create extension. The issue was originally disclosed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the pg_bigm extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

New features

• This version supports Babelfish 1.0.0 which extends your Amazon Aurora PostgreSQL database with the ability to accept database connections from Microsoft SQL Server clients. For more information, see Working with Babelfish for Aurora PostgreSQL.

Critical stability enhancements

• Fixed an issue where, in rare circumstances, a data cache of a read node may be inconsistent following a restart of that node.

High priority stability enhancements

• Fixed an issue where queries may become unresponsive due to I/O resource exhaustion triggered by prefetch.

• Fixed an issue where Aurora may flag an issue following a major version update with the message: "PANIC: could not access status of next transaction id xxxxxxxx".

Additional improvements and enhancements

• Fixed an issue where read nodes restart due to a replication origin cache lookup failure.

• Fixed an issue where read queries may time out on read nodes during the replay of lazy truncation triggered by vacuum on the write node.

• Fixed an issue that causes Performance Insights to incorrectly set the backend type of a database connection.

• Fixed an issue where the aurora_postgres_replica_status() function returned stale or lagging CPU stats.

• Fixed an issue where the role rds_superuser did not have permission to execute the pg_stat_statements_reset() function.

• Fixed an issue with the apg_plan_mgmt extension where the planning and execution times were reported as 0.

• Removed support for the DES, 3DES, and RC4 cipher suites.

• Updated the PostGIS extension to version 3.1.4.

• Updated the pgrouting extension to 3.1.3.

• Updated the pglogical extension to 2.4.0.

• Added support for the following SPI module extensions:

  • autoinc version 1.0

  • insert_username version 1.0

  • moddatetime version 1.0

  • refint version 1.0

• Fixed multiple issues in the Aurora storage daemon that could lead to brief periods of unavailability when specific network configurations are used.

• Fixed an out-of-memory crash issue with Aurora storage daemon that leads to writer node restart. This also reduces the overall system memory consumption.

General enhancements

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

Security enhancements

• Backpatched the PostgreSQL community fix for CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation". For more information, see CVE-2022-1552.

High priority stability enhancements

• Fixed an error handling issue related to out-of-memory conditions which could result in brief periods of unavailability.

• Fixed an issue that could cause excess storage use due to files not being properly closed.

• Fixed an issue that caused Performance Insights to show "Unknown wait event".

Security enhancements

• Includes additional modifications to the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

Security enhancements

• Modified the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the ip4r extension to mitigate a security issue during create extension. The issue was originally disclosed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Backpatched postgis to PostGIS 3.0.3. This is a PostGIS fix for the vulnerability addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

Security enhancements

• Modified the pg_bigm extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

Critical stability enhancements

• Fixed an issue where, in rare circumstances, a data cache of a read node may be inconsistent following a restart of that node.

High priority stability enhancements

• Fixed an issue where queries may become unresponsive due to I/O resource exhaustion triggered by prefetch.

• Fixed an issue where Aurora may flag an issue following a major version update with the message: "PANIC: could not access status of next transaction id xxxxxxxx".

Additional improvements and enhancements

• Fixed an issue where read nodes restart due to a replication origin cache lookup failure.

• Fixed an issue with the apg_plan_mgmt extension where the planning and execution times were reported as 0.

• Fixed an issue that causes Performance Insights to incorrectly set the backend type of a database connection.

• Fixed an issue with the apg_plan_mgmt extension where plan outline on a partitioned table did not enforce an index-based plan.

• Fixed an issue where orphaned files caused failed translations in read codepaths during or after a major version upgrade.

• Fixed multiple issues in the Aurora storage daemon that could lead to brief periods of unavailability when specific network configurations are used.

• Fixed an out-of-memory crash issue with Aurora storage daemon that leads to writer node restart. This also reduces the overall system memory consumption.

New features

• Supports a major version upgrade from PostgreSQL 12.4, Aurora PostgreSQL 4.0 (Deprecated) and later versions

• Supports bool_plperl version 1.0

• Supports rds_tools version 1.0

Critical stability enhancements

• Fixed an issue where, in rare circumstances, a data cache of a read node may be inconsistent following a restart of that node.

Additional improvements and enhancements

• Contains several improvements that were announced for PostgreSQL releases 13.0, 13.1, 13.2 and 13.3

• Instance type R4 was deprecated.

• Updated the following extensions:

  • hll to version 2.15.

  • hstore to version 1.7.

  • intarray to version 1.3.

  • log_fdw to version 1.2.

  • ltree to version 1.2.

  • pg_hint_plan to version 1.3.7.

  • pg_repack to version 1.4.6.

  • pg_stat_statements to version 1.8.

  • pg_trgm to version 1.5.

  • pgaudit to version 1.5.

  • pglogical to version 2.3.3.

  • pgrouting to version 3.1.0

  • plcoffee to version 2.3.15.

  • plls to version 2.3.15.

  • plv8 to version 2.3.15.

General enhancements

• Fixed a performance degradation issue in PLV8 extension.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue where pg_stat_statements can block minor version upgrade during ZDP.

• Fixed an issue where a logical replication slot would no longer emit changes due to an overly strict data consistency check.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

New features

• Amazon Bedrock integration – By using the Amazon Aurora machine learning extension with your Aurora PostgreSQLDB cluster, you can now use Amazon Bedrock foundational AI models.

• Delegated Extension Support – This feature allows delegating extension management to lower privileged user with the new rds_extension role.

• Query Plan Management (QPM) enhancements – Plan outlines will be updated to the latest format version as part of the update_plan_hash action for apg_plan_mgmt.validate_plans().

• Added support for the HypoPG extension at version 1.4.0.

• Added support for the h3-pg extension and the h3-postgis extension at version 4.1.3.

High priority enhancements

• Fixed an issue which may cause an Aurora replica to reboot when reading a page which was modified during WAL replay

• Fixed an issue where if a specific volume metadata is invalid on a source cluster, it will remain invalid on a cloned cluster. Since the clone cluster uses a new volume, the metadata will now be recreated.

• Fixed an issue which could, in rare cases, lead to an engine unavailable condition following a minor or patch version upgrade

• Fixed a bug that may cause an engine crash during zero-downtime patching (ZDP)

• Introduced a new parameter, rds.enable_memory_management, which is used to enable and disable the improved memory management feature.

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General enhancements

• Fixed an issue which may cause an Aurora replica to reboot while reconnecting with the writer DB instance.

• Added support for the rdkit.morgan_fp_size parameter

• Fixed an issue which may cause unused WAL segements to not be properly removed

• Fixed an issue where pglogical does not correctly pass-through replication origin data when using the binary output format

• Fixed a crash in dblink and postgres_fdw extensions due to invalid connections

• Fixed an issue where the aws_s3 extension can import HTTP error responses into the table

Additional improvements and enhancements

• Updated the following extensions:

  • mysql_fdw to version 2.9.1

  • Oracle_fdw to version 2.6.0

  • Orafce to version 4.6.0

  • pg_cron to version 1.6.0

  • pg_hint_plan to version 1.3.9

  • pg_proctab to version 0.0.10

  • plv8 to version 3.1.8

  • PostGIS to version 3.4.0

  • prefix to version 1.2.10

  • RDKit to version 4.4.0 (Release_2023_09_1)

General enhancements

• Fixed a performance degradation issue in PLV8 extension.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue where pg_stat_statements can block minor version upgrade during ZDP.

• Fixed an issue where a logical replication slot would no longer emit changes due to an overly strict data consistency check.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

New features

• Added support for mysql_fdw version 2.9.0

• Added support in the aws_s3 extension for exporting to an S3 bucket encrypted with a customer managed KMS key

• Improved the availability of Aurora replicas in the global DB secondary clusters

• Added support for query plan capture on Aurora replicas

• Allowed query plans under a given cost threshold to not be captured

General enhancements

• Fixed an issue in the aws_s3 extension where the number of rows exported is incorrectly reported when the total number exceeds 2 billion

• Provided options to configure timeouts in the aws_s3 extension. By setting the following parameters (GUCs), customers will now be able to change the timeout thresholds for imports from S3:

  • aws_s3.curlopt_low_speed_limit

  • aws_s3.curlopt_low_speed_time

• Improved the performance of replay of commit transaction operations on Aurora replicas

• Fixed an issue where, in rare cases, an import from the aws_s3 extension fails to complete

• Updated the GEOS library for PostGIS to version 3.12.0

• Added the WAIT_EVENT_Aurora_CLUSTER_CACHE_MANAGER_SENDER wait event to denote wait times in the cluster cache manager sender

• Added the WAIT_EVENT_Aurora_SERVERLESS_MONITORING_MAIN wait event to denote wait times in Aurora Serverless resource monitoring

• Fixed an issue where the database may crash during the start of a logical replication slot

• Increased the limit for pg_cron cron.max_running_jobs parameter from 100 to 1000

Additional improvements and enhancements

• Updated the following extensions:

  • orafce to version 4.3.0

  • pg_logical to version 2.4.3

  • pgvector to version 0.5.0

  • plv8 to version 3.1.6

  • PostGIS to version 3.3.3

  • RDKit to version 4.3

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue that would cause a logical replication slot to transiently error out in the presence of aborted subtransactions and DDL.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue that could result in read replica lag due to stale metadata

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

High priority stability enhancements

• Backported a fix for the following PostgreSQL community security issue:

  • CVE-2023-39417

High priority enhancements

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads.

• Fixed an issue which can cause vacuum operations to become blocked after the restart of an Aurora replica.

• Fixed an issue that would cause a crash when executing the COPY FROM command.

• Fixed an issue that would cause high CPU usage and prevent new connections.

• Fixed an issue where UPDATE and DELETE from a table with foreign key could fail unexpectedly with "ERROR: 40001: could not serialize access due to concurrent update when using Serializable snapshot".

General enhancements

• Introduced diagnostics for the transient metadata used for I/O.

• Updated the plv8, pll, and plcoffee extensions to version 2.3.15.

• Fixed an issue that prevented the enablement of improved memory management in certain scenarios in Aurora PostgreSQL 15.3.

New features

• This release contains memory management improvements which increase database stability and availability by proactively preventing issues caused by insufficient memory. For more information, see Improved memory management in Aurora PostgreSQL.

• Added support for the pgvector extension version 0.4.1.

High priority enhancements

• Fixed an issue with the subtransaction metadata handling when performing a survivable reader reconnect.

• Fixed an issue during ZDP which is related to the extension environment variables.

• Addressed a transient error during logical replication that caused a process to incorrectly calculate that it had encountered an unexpected page.

• Fixed an issue which causes a period of unavailability due to a partially created replication origin state file.

General enhancements

• Added a new function, aurora_stat_memctx_usage(), to show backend memory use breakdown at a Postgres memory context level.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters (GUCs), customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

• Fixed an issue with the calculation of the AuroraReplicaLag metric.

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots.

• Further reduced the database downtime during ZDP.

• Fixed a bug which can cause unavailability during ZDP.

• Fixed an issue which caused pg_ls_waldir() to return "ERROR: could not stat file".

• Added support for TLS 1.3 with ciphers TLS_AES_128_GCM_SHA256 and TLS_AES_256_GCM_SHA384.

• Addressed an issue that blocked a major version upgrade on the Aurora replica of an RDS for PostgreSQL DB instance.

• Fixed an issue in the pg_vector extension where, in rare cases, infinite or NAN values caused a crash during the index creation

• Upgraded GEOS to version 3.11.2.

• Upgraded pg_cron to version 1.5.

• Upgraded pg_partman to version 4.7.3.

• Upgraded tds_fdw to 2.0.3.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Fixed an issue that would cause a logical replication slot to transiently error out in the presence of aborted subtransactions and DDL.

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

General enhancements

• Fixed an issue that could result in read replica lag due to stale metadata

• Fixed an issue related to buffer pin locking that in rare cases can result in a crash

High priority stability enhancements

• Backported a fix for the following PostgreSQL community security issue:

  • CVE-2023-39417

High priority enhancements

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads.

• Fixed an issue which can cause vacuum operations to become blocked after the restart of an Aurora replica.

• Fixed an issue that would cause high CPU usage and prevent new connections.

General enhancements

• Introduced diagnostics for the transient metadata used for I/O.

• Updated the plv8, pll, and plcoffee extensions to version 2.3.15.

General enhancements

• Fixed an issue with the calculation of the AuroraReplicaLag metric

• Fixed a bug which can cause unavailability during ZDP

• Fixed an issue that prevented reclaiming storage on transaction commits

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase

• Added Aurora Serverless v2 scaling enhancements

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters (GUCs), customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

• Fixed multiple issues which can cause Aurora replicas with the improved read availability feature to restart when reconnecting with the writer instance.

• Fixed an issue preventing a survivable reader reconnect

General enhancements

• Fixed an error when loading the test_decoding plugin in pg_create_logical_replication_slot.

• Updated the Oracle client used by the oracle_fdw extension to version 21.9.0.0.0.

New features

• Introduced a new QPM plan hash calculation for multi-schema support. If users want to use QPM in multi-schema environments, they can set the apg_plan_mgmt.plan_hash version to 2 and call apg_plan_mgmt.validate_plans('update_plan_hash').

General enhancements

• Upgraded PROJ support to version 9.1.0

• Upgraded the GDAL library in PostGIS to version 3.5.3

• Added support for the TCN and SEG extensions

• Fixed an issue which may increase the amount of recovery work the database does to startup with logical replication enabled

• Improved performance of deletes from b-tree and hash indexes on Aurora replicas

• Fixed issues that caused incorrect I/O timing metrics in EXPLAIN

• Fixed an issue that caused incorrect buffer hit counts in EXPLAIN

• Improved the engine startup time, particularly on large instances with many objects

• The Aurora function aurora_stat_logical_wal_cache() is now visible to all users

• Fixed an issue in QPM that could cause unavailability when enforcing plans from prepared statements

Additional improvements and enhancements

• Updated the following extensions:

  • hll to version 2.17

  • Oracle_fdw to version 2.5.0

  • orafce to version 4.0.0

  • pg_cron to version 1.4.2

  • pg_hint_plan to version 1.3.8

  • pg_logical to version 2.4.2

  • pg_trgm to version 1.4

  • pgrouting to version 3.4.1

  • PostGIS to version 3.3.2

  • SEG to version 1.0

  • TCN to version 1.0

  • wal2json to version 2.5

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

High priority stability enhancements

• Fixed an issue which can cause a database instance to restart while executing IO intensive read workloads.

• Fixed an issue that would cause high CPU usage and prevent new connections.

General enhancements

• Introduced diagnostics for the transient metadata used for I/O.

General enhancements

• Added Aurora Serverless v2 scaling enhancements

• Fixed an issue in pg_cron which can prevent scaling in Aurora Serverless v2

• Fixed an issue with the calculation of the AuroraReplicaLag metric

• Fixed a bug which can cause unavailability during ZDP

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an Amazon S3 bucket with a name containing dots.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

• Updated the plv8, plls, and plcoffee extensions to version 2.3.15.

General stability enhancements

• Fixed an issue in PostGIS where the GDAL data wasn't loading.

• Fixed an issue that increased the amount of recovery work during startup if logical replication is enabled.

• Fixed an issue for the better error handling of procedures with large numbers of parameters.

• Fixed an issue with the aws_s3 extension where loading a large number of records can time out.

High priority stability enhancements

• Fixed an issue where an upgrade fails because the oldest MultiXactId is updated incorrectly.

• Fixed an issue where the commit latency metrics weren't updated.

• Fixed an issue that could lead to a brief period of unavailability.

General stability enhancements

• Fixed an issue that caused DB instance migration failures.

• Fixed an issue where the DB fails to start because of an inconsistency in the metadata.

• Improved the error handling and diagnosability.

• Upgraded the RDKit extension to version 4.2.

• Upgraded the GDAL library to version 3.4.3.

• The apg_plan_mgmt.copy_outline function now copies environment_variables.

• Fixed an issue that can cause certain processes to linger in an inconsistent state during a clean shutdown.

• Fixed an issue with the pg_repack extension.

• Improved the collation library (glibc) handling with a new independent default collation library.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39417

  • CVE-2023-2455

  • CVE-2023-2454

  • CVE-2022-41862

High priority enhancements

• Fixed an issue which blocked vacuum operations after the restart of an Aurora replica.

• Fixed an issue that would cause high CPU usage and prevent new connections.

General stability enhancements

• Fixed an issue which causes the stats collector process to repeatedly restart.

• Improved the scale times for Aurora Serverless v2.

• Fix a bug which can cause unavailability during ZDP.

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase.

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an S3 bucket with a name containing dots.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

• Fixed an issue which can cause a database instance to restart while executing I/O intensive read workloads.

• Updated the plv8, pll, and plcoffee extensions to version 2.3.15.

General stability enhancements

• Fixed an issue that increased the amount of recovery work during startup if logical replication is enabled.

• Fixed an issue for better error handling of procedures with large numbers of parameters.

• Fixed an issue with the aws_s3 extension where loading a large number of records can time out.

• Fixed an issue with the pg_cron parallel running of tasks.

General stability enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance.

• Fixed an issue where the engine experiences stability issues during database minor and patch release upgrades.

• Fixed an issue that could cause data inconsistency during replication.

General stability enhancements

• Added support for the rds_superuser role to execute CREATE OPERATOR CLASS, REATE OPERATOR FAMILY, and ALTER OPERATOR FAMILY, which are available in the higher versions.

• Improved buffer cache scavenging when the buffer cache is in duress.

• Fixed an issue in database activity streams that leads to high memory consumption.

• Fixed an issue that caused DB instance restarts.

• Fixed an issue where a DB instance restarts recursively while generating monitoring metrics during a crash.

• Fixed an issue where a DB instance restarted during performance metric collection.

• Fixed an issue where an attempt to connect to the database would fail with SSLV3_ALERT_CERTIFICATE_UNKNOWN.

• Improved the diagnostic logging around setting invalid hint bits.

• Fixed an issue where autovacuum would incorrectly skip tables.

• Improved the logical replication prefetching.

• Fixed a durability issue in the GIN indexes.

• Fixed an issue to detect and cancel stuck major version upgrades.

• Fixed an issue in hash join that could lead to increased memory consumption.

• Improved the logical replication performance.

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

• Upgraded the GEOS version to 3.10.3.

• Updated the PostGIS extension to version 3.2.3.

• Fixed an issue with st_orientedenvelope that caused it to loop with a 1-D input to return 0.

• Fixed an issue where the connection to SQL Server using tds_fdw fails.

General enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

High priority enhancements

• Backported fixes for the following PostgreSQL community security issue:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed a deadlock issue in Aurora Storage which can result in writer failover.

• Fixed an issue where active transactions during logical replication slot creation may be partially replicated by the slot.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39417

  • CVE-2023-2455

  • CVE-2023-2454

  • CVE-2022-41862

  • CVE-2022-2625

High priority enhancements

• Fixed an issue which blocked vacuum operations after the restart of an Aurora replica.

• Fixed an issue that would cause high CPU usage and prevent new connections.

General stability enhancements

• Fixed an issue which causes the stats collector process to repeatedly restart.

• Improved the scale times for Aurora Serverless v2.

• Fix a bug which can cause unavailability during ZDP.

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase.

• Fixed an issue where, in rare cases, the aws_s3 extension could fail to import from an S3 bucket with a name containing dots.

• Provided options to configure the timeouts within the aws_lambda extension. By setting the following parameters, customers will now be able to change the connect and request timeouts for Amazon Lambda integration:

  • aws_lambda.connect_timeout_ms.

  • aws_lambda.request_timeout_ms.

• Updated the plv8, pll, and plcoffee extensions to version 2.3.15.

General stability enhancements

• Fixed an issue where the engine experiences stability issues during database minor and patch release upgrades.

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

• Fixed an issue that could cause data inconsistency during replication.

High priority stability enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance.

High priority stability enhancements

• Fixed a PLV8 issue where the base parameter doesn't get loaded properly into the memory.

General stability enhancements

• Fixed a bug where Aurora PostgreSQL can't file the relfilenode.

• Fixed a stuck scaling issue when the current scaling event times out.

• Upgraded the PostGIS extension to version 3.1.7.

• Fixed an issue where extended query messages might be lost during zero-downtime patching (ZDP) causing the extended query to hang after the ZDP completion.

Critical stability enhancements

• Fixed an issue that could cause periods of unavailability during a storage node restart.

High priority stability enhancements

• Fixed an error handling issue related to out-of-memory conditions which could result in brief periods of unavailability.

• Fixed an issue when the connection to SQL Server fails using the TDS_FDW extension to query a foreign table.

• Fixed an issue that caused connections using the provided root certificate to fail.

• Improved the diagnostic and supportability information in case of inconsistent B-tree index entries.

New features

• Added support for the large object module (extension). For more information, see Managing large objects with the lo module.

• Added support for zero-downtime patching (ZDP) for minor version upgrades and patches. For more information, see Minor release upgrades and zero-downtime patching in the Amazon Aurora User Guide.

Critical updates

• Fixed a replay crash due to an LSN mismatch.

• Fixed the aws_s3 extension to prevent invalid region injection.

High stability updates

• Fixed multiple issues related to out-of-memory conditions which could result in brief periods of unavailability.

General stability updates

• Fixed a lock contention crash during an Aurora Serverless v1 scaling event.

• Fixed an issue where logical replication becomes stuck after a restart.

• Fixed multiple issues that could lead to brief periods of unavailability.

• Fixed a crash in pg_cron due to a task still running but being unscheduled.

• Fixed, during redo, an invalid page hit on the Generic Redo for GENERIC_XLOG_FULL_PAGE_DATA. This happens due to a timing hole between generating the log record and then writing the metadata for the record on the RW node and the RO node replays between those operations.

• Improved the query performance by supporting parallel workers.

• Upgraded the plugin wal2json version to 2.4.

• Upgraded the pglogical extension to version 2.4.1.

General enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance.

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

• Updated the PostGIS extension to version 3.1.7.

Security enhancements

• Backpatched the PostgreSQL community fix for CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation". For more information, see CVE-2022-1552.

Critical enhancements

• Fixed an issue during a storage node restart that could result in periods of unavailability.

High stability enhancements

• Fixed an error handling issue related to out-of-memory conditions that could result in brief periods of unavailability.

• Fixed an issue related to the existence of duplicate relation files that could result in periods of unavailability.

• Fixed a defect where the validation of cached plans may lead to a database restart when the plan was previously invalidated.

High priority stability enhancements

• Fixed an issue that could cause incorrect WriteIOPS reporting in the Amazon console.

• Fixed an issue that could cause unavailability after removal of a read node from a cluster.

General enhancements

• Fixed an issue that could cause an engine restart during periods of low free memory.

High priority stability enhancements

• Fixed multiple issues that may result in unavailability of a read node.

• Fixed an issue that may result in a read node being unable to replay WAL requiring the replication slot to be dropped and resynchronized.

• Fixed an issue that could cause excess storage use due to files not being properly closed.

General enhancements

• Fixed a small memory leak on read nodes when commit_ts is set.

• Fixed an issue that caused Performance Insights to show "Unknown wait event".

• Fixed an issue that could cause an import from Amazon S3 to fail when using the aws_s3 extension.

• Fixed multiple issues that could result in periods of unavailability when using apg_plan_mgmt.

• Fixed multiple issues that could result in periods of unavailability when QPM is enabled.

General stability enhancements

• Allow rds_superuser to terminate backends which are not explicitly associated with a role.

• Upgraded PLV8 extension to version 2.3.15.

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2024-0985

Critical stability enhancements

• Fixed an issue related to apg_plan_mgmt.

• Fixed an issue where active transactions during slot creation may be partially replicated by the slot.

• Fixed a deadlock issue in Aurora storage which can result in writer failover.

Critical stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-5870

  • CVE-2023-5869

  • CVE-2023-5868

General stability enhancements

• Fixed an issue with logical replication actions being performed by someone other than the table owner

Critical stability enhancements

• Backported a fix for the following security issue:

  • CVE-2023-38545

• Fixed an issue related to pg_cron background worker processes

High priority stability enhancements

• Backported fixes for the following PostgreSQL community security issues:

  • CVE-2023-39417

  • CVE-2023-2455

  • CVE-2023-2454

  • CVE-2022-41862

General enhancements

• Fixed an issue which causes the stats collector process to repeatedly restart.

• Fixed an issue preventing pglogical from logging conflicting rows during the apply phase.

General enhancements

• Fixed an issue that can cause increased network traffic when a writer instance transmits logs to a replica instance.

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

• Updated the PostGIS extension to version 3.1.7.

Security enhancements

• Backpatched the PostgreSQL community fix for CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation". For more information, see CVE-2022-1552.

Critical enhancements

• Fixed an issue during a storage node restart that could result in periods of unavailability.

High stability enhancements

• Fixed an error handling issue related to out-of-memory conditions that could result in brief periods of unavailability.

• Fixed an issue related to the existence of duplicate relation files that could result in periods of unavailability.

• Fixed an issue that could cause excess storage use due to files not being properly closed.

• Fixed an issue that caused Performance Insights to show "Unknown wait event".

Security enhancements

• Additional modifications to the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

General enhancements

• Fixed a bug that could cause an engine restart during periods of low free memory.

Security enhancements

• Updated the PostGIS extension from version 3.1.4 to 3.1.5. This update contains a PostGIS fix for the vulnerability addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the ip4r extension to mitigate a security issue during create extension. The issue was originally disclosed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the pg_bigm extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

Critical stability enhancements

• Fixed a bug where logical replication may hang resulting in the replay falling behind on the read node. The instance may eventually restart.

Additional improvements and enhancements

• Fixed a buffer cache bug that could cause brief periods of unavailability.

• Fixed a bug in the apg_plan_mgmt extension where an index based plan was not being enforced.

• Fixed a bug in the pg_logical extension that could cause brief periods of unavailability due to improper handling of NULL arguments.

• Fixed an issue where orphaned files caused major version upgrades to fail.

• Fixed incorrect Aurora Storage Daemon log write metrics.

• Fixed multiple bugs that could result in WAL replay falling behind and eventually causing the reader instances to restart.

• Improved the Aurora buffer cache page validation on reads.

• Improved the Aurora storage metadata validation.

• Updated the pg_cron extension to v1.4.

• Updated the pg_hint_pan extension to v1.3.7.

• For information about extensions and modules, see Extensions supported for Aurora PostgreSQL 12.

General enhancements

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

Security enhancements

• Backpatched the PostgreSQL community fix for CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation". For more information, see CVE-2022-1552.

General enhancements

• Fixed an error handling issue related to out-of-memory conditions which could result in brief periods of unavailability.

• Fixed an issue that could cause excess storage use due to files not being properly closed.

• Fixed an issue that could cause Performance Insights to display "Unknown wait event".

• Fixed an issue that could result in periods of unavailability due to the existence of duplicate relation files.

Security enhancements

• Additional modifications to the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

General enhancements

• Fixed a buffer cache bug that could cause brief periods of unavailability.

Security enhancements

• Updated the PostGIS extension from version 3.1.4 to 3.1.5. This update contains a PostGIS fix for the vulnerability addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the ip4r extension to mitigate a security issue during create extension. The issue was originally disclosed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the pg_bigm extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

Critical stability enhancements

• Fixed an issue where, in rare circumstances, a data cache of a read node may be inconsistent following a restart of that node.

High priority stability enhancements

• Fixed an issue where queries may become unresponsive due to I/O resource exhaustion triggered by prefetch.

• Fixed an issue where Aurora may flag an issue following a major version update with the message: "PANIC: could not access status of next transaction id xxxxxxxx".

Additional improvements and enhancements

• Fixed an issue where read nodes restart due to a replication origin cache lookup failure.

• Fixed an issue where read queries may time out on read nodes during the replay of lazy truncation triggered by vacuum on the write node.

• Fixed an issue that causes Performance Insights to incorrectly set the backend type of a database connection.

• Fixed an issue where the aurora_postgres_replica_status() function returned stale or lagging CPU stats.

• Fixed an issue where the role rds_superuser did not have permission to execute the pg_stat_statements_reset() function.

• Fixed an issue with the apg_plan_mgmt extension where the planning and execution times were reported as 0.

• Removed support for the DES, 3DES, and RC4 cipher suites.

• Updated PostGIS extension to version 3.1.4.

General enhancements

• Fixed an issue that causes database activity stream inconsistency when the monitoring agent is unavailable.

Security enhancements

• Backpatched the PostgreSQL community fix for CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation". For more information, see CVE-2022-1552.

High priority stability enhancements

• Fixed an error handling issue related to out-of-memory conditions which could result in brief periods of unavailability.

• Fixed an issue that could cause excess storage use due to files not being properly closed.

• Fixed an issue that caused Performance Insights to show "Unknown wait event".

Security enhancements

• Additional modifications to the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

Security enhancements

• Modified the pg_cron extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the pg_bigm extension to mitigate a security issue during create extension. The issue was addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Modified the ip4r extension to mitigate a security issue during create extension. The issue was originally disclosed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

• Backpatched the PostgreSQL community fix for CVE-2021-3677: “Memory disclosure in certain queries”. For more information, see CVE-2021-3677

• Backpatched postgis to PostGIS 3.0.3. This is a PostGIS fix for the vulnerability addressed in core PostgreSQL by CVE-2020-14350. For more information, see CVE-2020-14350.

Critical stability enhancements

• Fixed an issue where, in rare circumstances, a data cache of a read node may be inconsistent following a restart of that node.

High priority stability enhancements

• Fixed an issue where queries may become unresponsive due to I/O resource exhaustion triggered by prefetch.

• Fixed an issue where Aurora may flag an issue following a major version update with the message: "PANIC: could not access status of next transaction id xxxxxxxx".

Additional improvements and enhancements

• Fixed an issue where read nodes restart due to a replication origin cache lookup failure.

• Fixed an issue with the apg_plan_mgmt extension where planning and execution time were reported as 0.

• Fixed an issue that causes Performance Insights to incorrectly set the backend type of a database connection.

• Fixed an issue with the apg_plan_mgmt extension where plan outline on a partitioned table did not enforce an index-based plan.

• Fixed an issue where orphaned files caused failed translations in read codepaths during or after major version upgrade.

• Fixed multiple issues in the Aurora storage daemon that could lead to brief periods of unavailability when specific network configurations are used.

• Fixed an out-of-memory crash issue with Aurora storage daemon that leads to writer node restart. This also reduces the overall system memory consumption.