Amazon Aurora
User Guide for Aurora (API Version 2014-10-31)

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

Database Engine Versions for Amazon Aurora PostgreSQL

Following, you can find information about supported versions of the Aurora with PostgreSQL compatibility database engine. An Aurora database has two version numbers; the Aurora version number and the database engine version number. To determine the version numbers of your Aurora PostgreSQL database, see Identifying Your Version of Amazon Aurora PostgreSQL.

The following table shows the version of each Aurora PostgreSQL release and the PostgreSQL version that it is compatible with.

Aurora with PostgreSQL Compatibility Compatible PostgreSQL Release
Version 2.3 10.7
Version 2.2 10.6
Version 2.1 10.5
Version 2.0 10.4
Version 1.5 9.6.12
Version 1.4 9.6.11
Version 1.3 9.6.9
Version 1.2 9.6.8
Version 1.1 9.6.6 deprecated
Version 1.0 9.6.3 deprecated

The following Aurora PostgreSQL versions are supported.

Version 2.3

This version of Aurora PostgreSQL is compatible with PostgreSQL 10.7. For more information about the improvements in release 10.7, see PostgreSQL Release 10.7.

Version 2.3.5

You can find the following improvements in this engine update.

Improvements

  1. Fixed a bug that could cause DB instance restarts.

  2. Fixed a bug that could cause a crash when a backend exits while using logical replication.

  3. Fixed a bug that could cause a restart when reads occurred during failovers.

  4. Fixed a bug with the wal2json plugin for logical replication.

  5. Fixed a bug that could result in inconsistent metadata.

Version 2.3.3

You can find the following improvements in this engine update.

Improvements

  1. Provided a backport fix for the PostgreSQL community security issue CVE-2019-10130.

  2. Provided a backport fix for the PostgreSQL community security issue CVE-2019-10164.

  3. Fixed a bug whereby data activity streaming could consume excessive CPU time.

  4. Fixed a bug whereby parallel threads scanning a B-tree index could hang following a disk read.

  5. Fixed a bug where use of the not in predicate against a common table expression (CTE) could return the following error: "ERROR: bad levelsup for CTE".

  6. Fixed a bug whereby the read node replay process could hang while applying a modification to a generalized search tree (GiST) index.

  7. Fixed a bug whereby visibility map pages could contain incorrect freeze bits following a failover to a read node.

  8. Optimized log traffic between the write node and read nodes during index maintenance.

  9. Fixed a bug whereby queries on read nodes may crash while performing a B-tree index scan.

  10. Fixed a bug whereby a query that has been optimized for redundant inner join removal could crash.

  11. The function aurora_stat_memctx_usage now reports the number of instances of a given context name.

  12. Fixed a bug whereby the function aurora_stat_memctx_usage reported incorrect results.

  13. Fixed a bug whereby the read node replay process could wait to kill conflicting queries beyond the configured max_standby_streaming_delay value.

  14. Additional information is now logged on read nodes when active connections conflict with the relay process.

  15. Provided a backport fix for the PostgreSQL community bug #15677, where a crash could occur while deleting from a partitioned table.

Version 2.3.1

You can find the following improvements in this engine update.

Improvements

  1. Fixed multiple bugs related to I/O prefetching that caused engine crashes.

Version 2.3.0

You can find the following improvements in this engine update.

New Features

  1. Aurora PostgreSQL now performs I/O prefetching while scanning B-tree indexes. This results in significantly improved performance for B-tree scans over uncached data.

Improvements

  1. Fixed a bug whereby read nodes may fail with the error "too many LWLocks taken".

  2. Addressed numerous issues that caused read nodes to fail to startup while the cluster is under heavy write workload.

  3. Fixed a bug whereby usage of the aurora_stat_memctx_usage() function could lead to a crash.

  4. Improved the cache replacement strategy used by table scans to minimize thrashing of the buffer cache.

Version 2.2

This version of Aurora PostgreSQL is compatible with PostgreSQL 10.6. For more information about the improvements in release 10.6, see PostgreSQL Release 10.6.

Patch Versions

Version 2.2.1

You can find the following improvements in this engine update.

Improvements

  1. Improved stability of logical replication.

  2. Fixed a bug which could cause an error running queries. The message reported would be of the form "CLOG segment 123 does not exist: No such file or directory".

  3. Increased the supported size of IAM passwords to 8KB.

  4. Improved consistency of performance under high throughput write workloads.

  5. Fixed a bug which could cause a read replica to crash during a restart.

  6. Fixed a bug which could cause an error running queries. The message reported would be of the form "SQL ERROR: Attempting to read past EOF of relation".

  7. Fixed a bug which could cause an increase in memory usage after a restart.

  8. Fixed a bug which could cause a transaction with a large number of subtransactions to fail.

  9. Merged a patch from community PostgreSQL which addresses potential failures when using GIN indexes. For more information see https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f9e66f2fbbb49a493045c8d8086a9b15d95b8f18.

  10. Fixed a bug which could cause a snapshot import from RDS for PostgreSQL to fail.

Version 2.2.0

You can find the following improvements in this engine update.

New features

  1. Added the restricted password management feature. Restricted password management enables you to restrict who can manage user passwords and password expiration changes by using the parameter rds.restrict_password_commands and the role rds_password. For more information, see Restricting Password Management.

Version 2.1

This version of Aurora PostgreSQL is compatible with PostgreSQL 10.5. For more information about the improvements in release 10.5, see PostgreSQL Release 10.5.

Patch Versions

Version 2.1.1

You can find the following improvements in this engine update.

Improvements

  1. Fixed a bug which could cause an error running queries. The message reported would be of the form "CLOG segment 123 does not exist: No such file or directory".

  2. Increased the supported size of IAM passwords to 8KB.

  3. Improved consistency of performance under high throughput write workloads.

  4. Fixed a bug which could cause a read replica to crash during a restart.

  5. Fixed a bug which could cause an error running queries. The message reported would be of the form "SQL ERROR: Attempting to read past EOF of relation".

  6. Fixed a bug which could cause an increase in memory usage after a restart.

  7. Fixed a bug which could cause a transaction with a large number of subtransactions to fail.

  8. Merged a patch from community PostgreSQL which addresses potential failures when using GIN indexes. For more information see https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f9e66f2fbbb49a493045c8d8086a9b15d95b8f18.

  9. Fixed a bug which could cause a snapshot import from RDS for PostgreSQL to fail.

Version 2.1.0

You can find the following improvements in this engine update.

New features

  1. General availability of Aurora Query Plan Management, which enables customers to track and manage any or all query plans used by their applications, to control query optimizer plan selection, and to ensure high and stable applicationperformance. For more information, see Managing Query Execution Plans for Aurora PostgreSQL.

  2. Updated the libprotobuf extension to version 1.3.0. This is used by the PostGIS extension.

  3. Updated the pg_similarity extension to version 1.0.

  4. Updated the log_fdw extension to version 1.1.

  5. Updated the pg_hint_plan extension to version 1.3.1.

Improvements

  1. Network traffic between the writer and reader nodes is now compressed to reduce network utilization. This reduces the chance of read node unavailability due to network saturation.

  2. Implemented a high performance, scalable subsystem for PostgreSQL subtransactions. This improves the performance of applications which make extensive use of savepoints and PL/pgSQL exception handlers.

  3. The rds_superuser role can now set the following parameters on a per-session, database, or role level:

    • log_duration

    • log_error_verbosity

    • log_executor_stats

    • log_lock_waits

    • log_min_duration_statement

    • log_min_error_statement

    • log_min_messages

    • log_parser_stats

    • log_planner_stats

    • log_replication_commands

    • log_statement_stats

    • log_temp_files

  4. Fixed a bug whereby the SQL command "ALTER FUNCTION ... OWNER TO ..." might fail with error "improper qualified name (too many dotted names)".

  5. Fixed a bug whereby a crash could occur while committing a transaction with more than two million subtransactions.

  6. Fixed a bug in community PostgreSQL code related to GIN indexes which can cause the Aurora Storage volume to become unavailable.

  7. Fixed a bug whereby an Aurora PostgreSQL replica of an RDS for PostgreSQL instance might fail to start, reporting error: "PANIC: could not locate a valid checkpoint record".

  8. Fixed a bug whereby passing an invalid parameter to the aurora_stat_backend_waits function could cause a crash.

Known issues

  1. The pageinspect extension is not supported in Aurora PostgreSQL.

Version 2.0

This version of Aurora PostgreSQL is compatible with PostgreSQL 10.4. For more information about the improvements in release 10.4, see PostgreSQL Release 10.4.

Patch Versions

Version 2.0.1

You can find the following improvements in this engine update.

Improvements

  1. Fixed a bug which could cause an error running queries. The message reported would be of the form "CLOG segment 123 does not exist: No such file or directory".

  2. Increased the supported size of IAM passwords to 8KB.

  3. Improved consistency of performance under high throughput write workloads.

  4. Fixed a bug which could cause a read replica to crash during a restart.

  5. Fixed a bug which could cause an error running queries. The message reported would be of the form "SQL ERROR: Attempting to read past EOF of relation".

  6. Fixed a bug which could cause an increase in memory usage after a restart.

  7. Fixed a bug which could cause a transaction with a large number of subtransactions to fail.

  8. Merged a patch from community PostgreSQL which addresses potential failures when using GIN indexes. For more information see https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f9e66f2fbbb49a493045c8d8086a9b15d95b8f18.

  9. Fixed a bug which could cause a snapshot import from RDS for PostgreSQL to fail.

Version 2.0.0

You can find the following improvements in this engine update.

Improvements

  1. This release contains all fixes, features, and improvements present in Version 1.3.

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

  3. Updated the GDAL library, which is used by the PostGIS extension.

  4. Updated the ip4r extension to version 2.1.1.

  5. Updated the pg_repack extension to version 1.4.3.

  6. Updated the plv8 extension to version 2.1.2.

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

  8. Fixed a bug whereby read nodes may crash following a specific type of free space change from the write node.

Version 1.5

This version of Aurora PostgreSQL is compatible with PostgreSQL 9.6.12. For more information about the improvements in release 9.6.12, see PostgreSQL Release 9.6.12.

Version 1.5.3

You can find the following improvements in this engine update.

Improvements

  1. Fixed a bug that could cause DB instance restarts.

  2. Fixed a bug that could cause a restart when reads occurred during failovers.

  3. Fixed a bug that could result in inconsistent metadata.

Version 1.5.2

You can find the following improvements in this engine update.

Improvements

  1. Provided a backport fix for the PostgreSQL community security issue CVE-2019-10130.

  2. Fixed a bug whereby the read node replay process may hang while applying a modification to a generalized search tree (GiST) index.

  3. Fixed a bug whereby visibility map pages may contain incorrect freeze bits following a failover to a read node.

  4. Fixed a bug whereby the error "relation relation-name does not exist" is incorrectly reported.

  5. Optimized log traffic between the write node and read nodes during index maintenance.

  6. Fixed a bug whereby queries on read nodes may crash while performing a B-tree index scan.

  7. The function aurora_stat_memctx_usage now reports the number of instances of a given context name.

  8. Fixed a bug whereby the function aurora_stat_memctx_usage reported incorrect results.

  9. Fixed a bug whereby the read node replay process may wait to kill conflicting queries beyond the configured max_standby_streaming_delay.

  10. Additional information is now logged on read nodes when active connections conflict with the relay process.

Version 1.5.1

You can find the following improvements in this engine update.

Improvements

  1. Fixed multiple bugs related to I/O prefetching, which caused engine crashes.

Version 1.5.0

You can find the following improvements in this engine update.

New features

  1. Aurora PostgreSQL now performs I/O prefetching while scanning B-tree indexes. This results in significantly improved performance for B-tree scans over uncached data.

Improvements

  1. Addressed numerous issues that caused read nodes to fail to startup while the cluster is under heavy write workload.

  2. Fixed a bug whereby usage of the aurora_stat_memctx_usage() function could lead to a crash.

  3. Improved the cache replacement strategy used by table scans to minimize thrashing of the buffer cache.

Version 1.4

This version of Aurora PostgreSQL is compatible with PostgreSQL 9.6.11. For more information about the improvements in release 9.6.11, see PostgreSQL Release 9.6.11.

You can find the following improvements in this engine update.

New features

  1. Support is added for the pg_similarity extension version 1.0.

Improvements

  1. This release contains all fixes, features, and improvements present in Version 1.3.

  2. Network traffic between the writer and reader nodes is now compressed to reduce network utilization. This reduces the chance of read node unavailability due to network saturation.

  3. Performance of subtransactions has improved under high concurrency workloads.

  4. An update for the pg_hint_plan extension to version 1.2.3.

  5. Fixed an issue where on a busy system, a commit with millions of subtransactions (and sometimes with commit timestamps enabled) can cause Aurora to crash.

  6. Fixed an issue where an INSERT statement with VALUES could fail with the message "Attempting to read past EOF of relation".

  7. An upgrade of the apg_plan_mgmt extension to version 1.0.1. The apg_plan_mgmt extension is used with query plan management. For more about how to install, upgrade, and use the apg_plan_mgmt extension, see Managing Query Execution Plans for Aurora PostgreSQL.

    The apg_plan_mgmt extension new features include the following:

    1. A new update_plan_hash parameter is available for the validate_plans function. This parameter updates the plan_hash for plans that can't be reproduced exactly. The update_plan_hash parameter also enables you to fix a plan by rewriting the SQL. You can then register the good plan as an Approved plan for the original SQL. Following is an example of using update_plan_hash.

      UPDATE apg_plan_mgmt.dba_plans SET plan_hash = new _plan_hash, plan_outline = good_plan_outline WHERE sql_hash = bad_plan_sql_hash AND plan_hash = bad_plan_plan_hash; SELECT apg_plan_mgmt.validate_plans(bad_plan_sql_hash, bad_plan_plan_hash, 'update_plan_hash'); SELECT apg_plan_mgmt.reload();
    2. A new get_explain_stmt function is available that generates the text of an EXPLAIN statement for the specified SQL statement. It includes the parameters sql_hash, plan_hash and explain_options.

      The parameter explain_options can be any comma-separated list of valid EXPLAIN options, as shown following.

      analyze,verbose,buffers,hashes,format json

      If the parameter explain_options is NULL or an empty string, the get_explain_stmt function generates a simple EXPLAIN statement.

      To create an EXPLAIN script for your workload or a portion of it, use the \a , \t, and \o options to redirect the output to a file. For example, you can create an EXPLAIN script for the top-ranked (top-K) statements by using the PostgreSQL pg_stat_statements view sorted by total_time in DESC order.

    3. The precise location of the Gather parallel query operator is determined by costing, and may change slightly over time. To prevent these differences from invalidating the entire plan, query plan management now computes the same plan_hash even if the Gather operators move to different places in the plan tree.

    4. Support is added for nonparameterized statements inside pl/pgsql functions.

    5. Overhead is reduced when the apg_plan_mgmt extension is installed on multiple databases in the same cluster while two or more databases are being accessed concurrently. Also, this release fixed a bug in this area that caused plans to not be stored in shared memory.

    The apg_plan_mgmt extension improvements include the following:

    1. Improvements to the evolve_plan_baselines function.

      1. The evolve_plan_baselines function now computes a cardinality_error metric over all nodes in the plan. Using this metric, you can identify any plan where the cardinality estimation error is large, and the plan quality is more doubtful. Long-running statements with high cardinality_error values are high-priority candidates for query tuning.

      2. Reports generated by evolve_plan_baselines now include sql_hash, plan_hash, and the plan status.

      3. You can now allow evolve_plan_baselines to approve previously Rejected plans.

      4. The meaning of speedup_factor for evolve_plan_baselines is now always relative to the baseline plan. For example, a value of 1.1 now means 10 percent faster than the baseline plan. A value of 0.9 means 10 percent slower than the baseline plan. The comparison is made using execution time alone instead of total time.

      5. The evolve_plan_baselines function now warms the cache in a new way. It does this by running the baseline plan, then running the baseline plan one more time, and then running the candidate plan once. Previously, evolve_plan_baselines ran the candidate plan twice. This approach added significantly to execution time, especially for slow candidate plans. However, running the candidate plan twice is more reliable when the candidate plan uses an index that isn't used in the baseline plan.

    2. Query plan management no longer saves plans that refer to system tables or views, temporary tables, or the query plan management's own tables.

    3. Bug fixes include caching a plan immediately when saved and fixing a bug that caused the back end to terminate.

Version 1.3

This version of Aurora PostgreSQL is compatible with PostgreSQL 9.6.9. For more information about the improvements in version 9.6.9, see PostgreSQL Release 9.6.9.

Patch Versions

Version 1.3.2

You can find the following improvements in this engine update.

New features

  1. Added the ProcArrayGroupUpdate wait event.

Improvements

  1. Fixed a bug which could cause an error running queries. The message reported would be of the form "CLOG segment 123 does not exist: No such file or directory".

  2. Increased the supported size of IAM passwords to 8KB.

  3. Improved consistency of performance under high throughput write workloads.

  4. Fixed a bug which could cause a read replica to crash during a restart.

  5. Fixed a bug which could cause an error running queries. The message reported would be of the form "SQL ERROR: Attempting to read past EOF of relation".

  6. Fixed a bug which could cause an increase in memory usage after a restart.

  7. Fixed a bug which could cause a transaction with a large number of subtransactions to fail.

  8. Merged a patch from community PostgreSQL which addresses potential failures when using GIN indexes. For more information see https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f9e66f2fbbb49a493045c8d8086a9b15d95b8f18.

  9. Fixed a bug which could cause a snapshot import from RDS for PostgreSQL to fail.

Version 1.3.0

You can find the following improvements in this engine update.

Improvements

  1. This release contains all fixes, features, and improvements present in Version 1.2.

  2. Updated the GDAL library, which is used by the PostGIS extension.

  3. Updated the following PostgreSQL extensions:

    • ip4r updated to version 2.1.1.

    • pgaudit updated to version 1.1.1.

    • pg_repack updated to version 1.4.3.

    • plv8 updated to version 2.1.2.

  4. Fixed an issue in the monitoring system that could incorrectly cause a failover when local disk usage is high.

  5. Fixed a bug whereby Aurora PostgreSQL can repeatedly crash, reporting:

    PANIC: new_record_total_len (8201) must be less than BLCKSZ (8192), rmid (6), info (32)

  6. Fixed a bug whereby an Aurora PostgreSQL read node might be unable to rejoin a cluster due to recovery of a large buffer cache. This issue is unlikely to occur on instances other than r4.16xlarge.

  7. Fixed a bug whereby inserting into an empty GIN index leaf page imported from pre-9.4 engine versions can cause the Aurora storage volume to become unavailable.

  8. Fixed a bug whereby, in rare circumstances, a crash during transaction commit could result in the loss of CommitTs data for the committing transaction. The actual durability of the transaction was not impacted by this bug.

  9. Fixed a bug in the PostGIS extension whereby PostGIS can crash in the function gserialized_gist_picksplit_2d().

  10. Improved the stability of read-only nodes during heavy write traffic on instances smaller than r4.8xl. This specifically addresses a situation where the network bandwidth between the writer and the reader is constrained.

  11. Fixed a bug whereby an Aurora PostgreSQL instance acting as a replication target of an RDS for PostgreSQL instance crashed with the following error:

    FATAL: could not open file "base/16411/680897_vm": No such file or directory" during "xlog redo at 782/3122D540 for Storage/TRUNCATE"

  12. Fixed a memory leak on read-only nodes whereby the heap size for the "aurora wal replay process" will continue to grow. This is observable via Enhanced Monitoring.

  13. Fixed a bug whereby Aurora PostgreSQL can fail to start, with the following message reported in the PostgreSQL log:

    FATAL: Storage initialization failed.

  14. Fixed a performance limitation on heavy write workloads that caused waits on the LWLock:buffer_content and IO:ControlFileSyncUpdate events.

  15. Fixed a bug whereby read nodes could crash following a specific type of free space change from the write node.

Version 1.2

This version of Aurora PostgreSQL is compatible with PostgreSQL 9.6.8. For more information about the improvements in version 9.6.8, see PostgreSQL Release 9.6.8.

Patch Versions

Version 1.2.2

You can find the following improvements in this engine update.

New features

  1. Added the ProcArrayGroupUpdate wait event.

Improvements

  1. Fixed a bug which could cause an error running queries. The message reported would be of the form "CLOG segment 123 does not exist: No such file or directory".

  2. Increased the supported size of IAM passwords to 8KB.

  3. Improved consistency of performance under high throughput write workloads.

  4. Fixed a bug which could cause a read replica to crash during a restart.

  5. Fixed a bug which could cause an error running queries. The message reported would be of the form "SQL ERROR: Attempting to read past EOF of relation".

  6. Fixed a bug which could cause an increase in memory usage after a restart.

  7. Fixed a bug which could cause a transaction with a large number of subtransactions to fail.

  8. Merged a patch from community PostgreSQL which addresses potential failures when using GIN indexes. For more information see https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f9e66f2fbbb49a493045c8d8086a9b15d95b8f18.

  9. Fixed a bug which could cause a snapshot import from RDS for PostgreSQL to fail.

Version 1.2.0

You can find the following improvements in this engine update.

New features

  1. Introduced the aurora_stat_memctx_usage() function. This function reports internal memory context usage for each PostgreSQL backend. You can use this function to help determine why certain backends are consuming large amounts of memory.

Improvements

  1. This release contains all fixes, features, and improvements present in Version 1.1.

  2. Updates the following PostgreSQL extensions:

    • pg_hint_plan updated to version 1.2.2

    • plv8 updated to version 2.1.0

  3. Improves efficiency of traffic between writer and reader nodes.

  4. Improves connection establishment performance.

  5. Improve the diagnostic data provided in the PostgreSQL error log when an out-of-memory error is encountered.

  6. Multiple fixes to improve the reliability and performance of snapshot import from Amazon RDS for PostgreSQL to Aurora with PostgreSQL compatibility.

  7. Multiple fixes to improve the reliability and performance of Aurora PostgreSQL read nodes.

  8. Fixes a bug in which an otherwise idle instance can generate unnecessary read traffic on an Aurora storage volume.

  9. Fixes a bug in which duplicate sequence values can be encountered during insert. The problem only occurs when migrating a snapshot from RDS for PostgreSQL to Aurora PostgreSQL. The fix prevents the problem from being introduced when performing the migration. Instances migrated before this release can still encounter duplicate key errors.

  10. Fixes a bug in which an RDS for PostgreSQL instance migrated to Aurora PostgreSQL using replication can run out of memory doing insert/update of GIST indexes, or cause other issues with GIST indexes.

  11. Fixes a bug in which vacuum can fail to update the corresponding pg_database.datfrozenxid value for a database.

  12. Fixes a bug in which a crash while creating a new MultiXact (contended row level lock) can cause Aurora PostgreSQL to hang indefinitely on the first access to the same relation after the engine restarts.

  13. Fixes a bug in which a PostgreSQL backend can't be terminated or canceled while invoking an fdw call.

  14. Fixes a bug in which one vCPU is fully utilized at all times by the Aurora storage daemon. This issue is especially noticeable on smaller instance classes, such as r4.large, where it can lead to 25–50 percent CPU usage when idle.

  15. Fixes a bug in which an Aurora PostgreSQL writer node can fail over spuriously.

  16. Fixes a bug in which, in a rare scenario, an Aurora PostgreSQL read node can report:

    "FATAL: lock buffer_io is not held"

  17. Fixes a bug in which stale relcache entries can halt vacuuming of relations and push the system close to transaction ID wraparound. The fix is a port of a PostgreSQL community patch scheduled to be released in a future minor version.

  18. Fixes a bug in which a failure while extending a relation can cause Aurora to crash while scanning the partially extended relation.

Version 1.1

This version of Aurora PostgreSQL is compatible with PostgreSQL 9.6.6. For more information about the improvements in version 9.6.6 see, PostgreSQL Release 9.6.6.

You can find the following improvements in this engine update:

New features

  1. Introduced the aurora_stat_utils extension. This extension includes two functions:

    • aurora_wait_report() function for wait event monitoring

    • aurora_log_report() for log record write monitoring

  2. Added support for the following extensions:

    • orafce 3.6.1

    • pgrouting 2.4.2

    • postgresql-hll 2.10.2

    • prefix 1.2.6

Improvements

  1. This release contains all fixes, features, and improvements present in Version 1.0.11

  2. Updates for the following PostgreSQL extensions:

    • postgis extension updated to version 2.3.4

    • geos library updated to version 3.6.2

    • pg_repack updated to version 1.4.2

  3. Access to the pg_statistic relation enabled.

  4. Disabled the 'effective_io_concurrency' guc parameter, as it does not apply to Aurora storage.

  5. Changed the 'hot_standby_feedback' guc parameter to not-modifiable and set the value to '1'.

  6. Improved heap page read performance during a vacuum operation.

  7. Improved performance of snapshot conflict resolution on read nodes.

  8. Improved performance of transaction snapshot acquisition on read nodes.

  9. Improved write performance for GIN meta page updates.

  10. Improved buffer cache recovery performance during startup.

  11. Fixes a bug that caused a database engine crash at startup while recovering prepared transactions.

  12. Fixes a bug that could result in the inability to start a read node when there are a large number of prepared transactions.

  13. Fixes a bug that could cause a read node to report:

    ERROR: could not access status of transaction 6080077

    DETAIL:* *Could not open file "pg_subtrans/005C": No such file or directory.

  14. Fixes a bug that could cause the error below when replicating from RDS PostgreSQL to Aurora PostgreSQL:

    FATAL: lock buffer_content is not held

    CONTEXT: xlog redo at 46E/F1330870 for Storage/TRUNCATE: base/13322/8058750 to 0 blocks flags 7

  15. Fixes a bug that could cause Aurora PostgreSQL to hang while replaying a multixact WAL record when replicating from RDS PostgreSQL to Aurora PostgreSQL.

  16. Multiple improvements to the reliability of importing snapshots from RDS PostgreSQL to Aurora PostgreSQL.

Version 1.0

This version of Aurora PostgreSQL is compatible with PostgreSQL 9.6.3. For more information about the improvements in version 9.6.3 see, PostgreSQL Release 9.6.3.

This version includes the following patch versions:

Version 1.0.11

You can find the following improvements in this engine update:

  1. Fixes an issue with parallel query execution that can lead to incorrect results.

  2. Fixes an issue with visibility map handling during replication from Amazon RDS for PostgreSQL that can cause the Aurora storage volume to become unavailable.

  3. Corrects the pg-repack extension.

  4. Implements improvements to maintain fresh nodes.

  5. Fixes issues that can lead to an engine crash.

Version 1.0.10

This update includes a new feature. You can now replicate an Amazon RDS PostgreSQL DB instance to Aurora PostgreSQL. For more information, see Replication with Amazon Aurora PostgreSQL.

You can find the following improvements in this engine update:

  1. Adds error logging when a cache exists and a parameter change results in a mismatched buffer cache, storage format, or size.

  2. Fixes an issue that causes an engine reboot if there is an incompatible parameter value for huge pages.

  3. Improves handling of multiple truncate table statements during a replay of a write ahead log (WAL) on a read node.

  4. Reduces static memory overhead to reduce out-of-memory errors.

  5. Fixes an issue that can lead to out-of-memory errors while performing an insert with a GiST index.

  6. Improves snapshot import from RDS PostgreSQL, removing the requirement that a vacuum be performed on uninitialized pages.

  7. Fixes an issue that causes prepared transactions to return to the previous state following an engine crash.

  8. Implements improvements to prevent read nodes from becoming stale.

  9. Implements improvements to reduce downtime with an engine restart.

  10. Fixes issues that can cause an engine crash.

Version 1.0.9

In this engine update, we fix an issue that can cause the Aurora storage volume to become unavailable when importing a snapshot from RDS PostgreSQL that contained uninitialized pages.

Version 1.0.8

You can find the following improvements in this engine update:

  1. Fixes an issue that prevented the engine from starting if the shared_preload_libraries instance parameter contained pg_hint_plan.

  2. Fixes the error "Attempt to fetch heap block XXX is beyond end of heap (YYY blocks)," which can occur during parallel scans.

  3. Improves the effectiveness of prefetching on reads for a vacuum.

  4. Fixes issues with snapshot import from RDS PostgreSQL, which can fail if there are incompatible pg_internal.init files in the source snapshot.

  5. Fixes an issue that can cause a read node to crash with the message "aurora wal replay process (PID XXX) was terminated by signal 11: Segmentation fault". This issue occurs when the reader applied a visibility map change for an uncached visibility map page.

Version 1.0.7

This is the first generally available release of Amazon Aurora with PostgreSQL compatibility.