PostgreSQL On Amazon RDS

10/1/2019 PostgreSQL on Amazon RDS - Amazon Relational Database Service
AWS Documentation (/index.html) » Amazon Relational Database Service (RDS) (/rds/index.html) » User Guide (index.html) »
PostgreSQL on Amazon RDS
The AWS Documentation website is getting a new look!

Try it now and let us know what you think. Switch to the new look >>
(/en_pv/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html)
You can return to the original look by selecting English in the language selector above.
PostgreSQL on Amazon RDS
Amazon RDS supports DB instances running several versions of PostgreSQL. You can create
DB instances and DB snapshots, point-in-time restores and backups. DB instances running
PostgreSQL support Multi-AZ deployments, Read Replicas (version 9.3.5 and later),
Provisioned IOPS, and can be created inside a VPC. You can also use Secure Socket Layer (SSL)
to connect to a DB instance running PostgreSQL.
Before creating a DB instance, you should complete the steps in the Setting Up for Amazon
RDS (CHAP_SettingUp.html) section of this guide.
You can use any standard SQL client application to run commands for the instance from your
client computer. Such applications include pgAdmin, a popular Open Source administration
and development tool for PostgreSQL, or psql, a command line utility that is part of a
PostgreSQL installation. To deliver a managed service experience, Amazon RDS doesn't
provide host access to DB instances, and it restricts access to certain system procedures and
tables that require advanced privileges. Amazon RDS supports access to databases on a DB
instance using any standard SQL client application. Amazon RDS doesn't allow direct host
access to a DB instance by using Telnet or Secure Shell (SSH).
Amazon RDS for PostgreSQL is compliant with many industry standards. For example, you
can use Amazon RDS for PostgreSQL databases to build HIPAA-compliant applications and to
store healthcare-related information, including protected health information (PHI) under an
executed Business Associate Agreement (BAA) with AWS. Amazon RDS for PostgreSQL also
meets Federal Risk and Authorization Management Program (FedRAMP) security
requirements. Amazon RDS for PostgreSQL has received a FedRAMP Joint Authorization
Board (JAB) Provisional Authority to Operate (P-ATO) at the FedRAMP HIGH Baseline within
the AWS GovCloud (US-West) Region. For more information on supported compliance
standards, see AWS Cloud Compliance (https://aws.amazon.com/compliance/) .
To import PostgreSQL data into a DB instance, follow the information in the Importing Data
into PostgreSQL on Amazon RDS (PostgreSQL.Procedural.Importing.html) section.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html 1/72
Topics
Common Management Tasks for PostgreSQL on Amazon RDS

(#CHAP_PostgreSQL.CommonTasks)
Creating a DB Instance Running the PostgreSQL Database Engine
(USER_CreatePostgreSQLInstance.html)
Connecting to a DB Instance Running the PostgreSQL Database Engine
(USER_ConnectToPostgreSQLInstance.html)
Modifying a DB Instance Running the PostgreSQL Database Engine
(USER_ModifyPostgreSQLInstance.html)
Upgrading the PostgreSQL DB Engine for Amazon RDS
(USER_UpgradeDBInstance.PostgreSQL.html)
Working with PostgreSQL Read Replicas (USER_PostgreSQL.Replication.ReadReplicas.html)
Importing Data into PostgreSQL on Amazon RDS (PostgreSQL.Procedural.Importing.html)
Common DBA Tasks for PostgreSQL (Appendix.PostgreSQL.CommonDBATasks.html)
Working with the Database Preview Environment (#working-with-the-database-preview-
environment)
Amazon RDS for PostgreSQL Versions and Extensions (#PostgreSQL.Concepts)
Common Management Tasks for PostgreSQL on Amazon RDS
The following are the common management tasks you perform with an Amazon RDS for
PostgreSQL DB instance, with links to relevant documentation for each task.
Task Area
Setting up Amazon RDS for rst-time use
There are prerequisites you must complete before you create your DB instance. For example, D
instances are created by default with a rewall that prevents access to it. You therefore must
create a security group with the correct IP addresses and network con guration to access the
DB instance.
Understanding Amazon RDS DB instances
If you are creating a DB instance for production purposes, you should understand how instanc
classes, storage types, and Provisioned IOPS work in Amazon RDS.
Finding supported PostgreSQL versions
Amazon RDS supports several versions of PostgreSQL.
Setting up high availability and failover support
A production DB instance should use Multi-AZ deployments. Multi-AZ deployments provide

increased availability, data durability, and fault tolerance for DB instances.
Understanding the Amazon Virtual Private Cloud (VPC) network
If your AWS account has a default VPC, then your DB instance is automatically created inside
the default VPC. In some cases, your account might not have a default VPC, and you might
want the DB instance in a VPC. In these cases, create the VPC and subnet groups before you
create the DB instance.
Importing data into Amazon RDS PostgreSQL
You can use several di erent tools to import data into your PostgreSQL DB instance on Amaz
RDS.
Setting up read-only Read Replicas (masters and standbys)
PostgreSQL on Amazon RDS supports Read Replicas in both the same AWS Region and in a
di erent AWS Region from the master instance.
Understanding security groups
By default, DB instances are created with a rewall that prevents access to them. You therefor
must create a security group with the correct IP addresses and network con guration to acces
the DB instance.
In general, if your DB instance is on the EC2-Classic platform, you need to create a DB security
group. If your DB instance is on the EC2-VPC platform, you need to create a VPC security grou
Setting up parameter groups and features
If your DB instance is going to require speci c database parameters, you should create a
parameter group before you create the DB instance.
Performing common DBA tasks for PostgreSQL
Some of the more common tasks for PostgreSQL DBAs include:
Creating Roles
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.Roles)
Managing PostgreSQL Database Access
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.Access)
Working with PostgreSQL Parameters

(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.Parameter
Working with PostgreSQL Autovacuum on Amazon RDS
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.Autovacuu
Audit Logging for a PostgreSQL DB Instance
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.Auditing)
Working with PostGIS
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.PostGIS)
Using pgBadger for Log Analysis with PostgreSQL
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.Badger)
Using a Custom DNS Server for Outbound Network Access
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.CustomDN
Connecting to your PostgreSQL DB instance
After creating a security group and associating it to a DB instance, you can connect to the DB
instance using any standard SQL client application such as pgadmin III.
Backing up and restoring your DB instance
You can con gure your DB instance to take automated backups, or take manual snapshots, an
then restore instances from the backups or snapshots.
Monitoring the activity and performance of your DB instance
You can monitor a PostgreSQL DB instance by using CloudWatch Amazon RDS metrics, events
and enhanced monitoring.
Upgrading the PostgreSQL database version
You can do both major and minor version upgrades for your PostgreSQL DB instance.
Working with log les
You can access the log les for your PostgreSQL DB instance.
Understanding the best practices for PostgreSQL DB instances
Find some of the best practices for working with PostgreSQL on Amazon RDS.
Working with the Database Preview Environment
When you create a DB instance in Amazon RDS, you know that the PostgreSQL version it's
based on has been tested and is fully supported by Amazon. The PostgreSQL community
releases new versions and new extensions continuously. You can try out new PostgreSQL
versions and extensions before they are fully supported. To do that, you can create a new DB
instance in the Database Preview Environment.
DB instances in the Database Preview Environment are similar to DB instances in a production

environment. However, keep in mind several important factors:
All DB instances are deleted 60 days after you create them, along with any backups and
snapshots.
You can only create a DB instance in a virtual private cloud (VPC) based on the Amazon
VPC service.
You can only create M4, T2, and R4 instance types. For more information about RDS
instance classes, see Choosing the DB Instance Class (Concepts.DBInstanceClass.html) .
You can't get help from AWS Support with DB instances. You can post your questions in
the RDS Database Preview Environment Forum
(https://forums.aws.amazon.com/forum.jspa?forumID=301) .
You can only use General Purpose SSD and Provisioned IOPS SSD storage.
You can't copy a snapshot of a DB instance to a production environment.
Some Amazon RDS features aren't available in the preview environment, as described
following.
Topics
Features Not Supported in the Preview Environment (#preview-environment-exclusions)

PostgreSQL Extensions Supported in the Preview Environment (#preview-environment-
extensions)
Creating a New DB Instance in the Preview Environment (#create-db-instance-in-preview-
environment)
Features Not Supported in the Preview Environment
The following features are not available in the preview environment:
Cross-region snapshot copy

Cross-region Read Replicas
Extensions not in the following table of supported extensions
PostgreSQL Extensions Supported in the Preview Environment
The PostgreSQL extensions supported in the Database Preview Environment are listed in the
following table.
Extension Version
amcheck 1.1
bloom 1.0
btree_gin 1.3
btree_gist 1.5
citext 1.5
cube 1.4
dblink 1.2
dict_int 1.0
dict_xsyn 1.0
earthdistance 1.1
fuzzystrmatch 1.1
hstore 1.5
hstore_plper 1.0
intagg 1.1
antarray 1.2
isn 1.2
log_fdw 1.0
ltree 1.1
pg_bu ercache 1.3
pg_freespacemap 1.2
pg_prewarm 1.2
pg_stat_statements 1.5
pg_trgm 1.4
pg_visibility 1.2
pgcrypto 1.3
pgrowlocks 1.2
pgstattuple 1.5
plperl 1.0
plpgsql 1.0
pltcl 1.0
postgres_fdw 1.0
sslinfo 1.2
tablefunc 1.0
test_parser 1.0
tsm_system_rows 1.0
tsm_system_time 1.0
unaccent 1.1
uuid_ossp 1.1
Creating a New DB Instance in the Preview Environment
Use the following procedure to create a DB instance in the preview environment.
To create a DB instance in the preview environment
1. Sign in to the AWS Management Console and open the Amazon RDS console at
https://console.aws.amazon.com/rds/ (https://console.aws.amazon.com/rds/) .
2. Choose Dashboard from the navigation pane.
3. Choose Switch to database preview environment.
You also can navigate directly to the Database Preview Environment (https://us-east-
2.console.aws.amazon.com/rds-preview/home?region=us-east-2#) .
Note
If you want to create an instance in the Database Preview Environment with

the API or CLI the endpoint is rds-preview.us-east-2.amazonaws.com.
4. Continue with the procedure as described in New Console

(USER_CreatePostgreSQLInstance.html#USER_CreatePostgreSQLInstance.CON) .
Amazon RDS for PostgreSQL Versions and Extensions
Amazon RDS supports DB instances running several editions of PostgreSQL. Use this section
to see how to work with PostgreSQL on Amazon RDS. You should also be aware of the limits
for PostgreSQL DB instances.
You can specify any currently supported PostgreSQL version when creating a new DB
instance. You can specify the major version (such as PostgreSQL 10), and any supported
minor version for the speci ed major version. If no version is speci ed, Amazon RDS defaults
to a supported version, typically the most recent version. If a major version is speci ed but a
minor version is not, Amazon RDS defaults to a recent release of the major version you have
speci ed. To see a list of supported versions, as well as defaults for newly created DB
instances, use the describe-db-engine-versions
(https://docs.aws.amazon.com/cli/latest/reference/rds/describe-db-engine-versions.html) AWS CLI
command.
For information about importing PostgreSQL data into a DB instance, see Importing Data into
PostgreSQL on Amazon RDS (PostgreSQL.Procedural.Importing.html) .
Topics
Supported PostgreSQL Database Versions (#PostgreSQL.Concepts.General.DBVersions)

Supported PostgreSQL Features and Extensions
(#PostgreSQL.Concepts.General.FeaturesExtensions)
Supported PostgreSQL Database Versions
Amazon RDS supports the following PostgreSQL versions.
Topics
PostgreSQL Version 12 Beta 3 on Amazon RDS in the Database Preview Environment

(#PostgreSQL.Concepts.General.version12beta3)
(#PostgreSQL.Concepts.General.version12)
PostgreSQL Version 11.4 on Amazon RDS (#PostgreSQL.Concepts.General.version114)
PostgreSQL Version 11 on Amazon RDS in the Database Preview Environment
(#PostgreSQL.Concepts.General.version11)
PostgreSQL Version 9.6.14 on Amazon RDS (#PostgreSQL.Concepts.General.version9614)

PostgreSQL version 12 Beta 3 contains several improvements that are described in

PostgreSQL 12 Beta 3 Released! (https://www.postgresql.org/about/news/1960/)
For information on the Database Preview Environment, see Working with the Database
Preview Environment (CHAP_PostgreSQL.html#working-with-the-database-preview-environment) .
To access the Preview Environment from the console, select
https://console.aws.amazon.com/rds-preview/ (https://console.aws.amazon.com/rds-preview/) .
For information on extensions supported in this version, see PostgreSQL Version 12.x
Extensions and Modules Supported on Amazon RDS in the Database Preview Environment
(CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.Extensions.12x) .
PostgreSQL version 12 Beta 2 contains several improvements that are described in the
following links:

PostgreSQL Version 11.4 on Amazon RDS
This release contains an important security x and also bug xes and improvements done by
the PostgreSQL community. For more information on the security x, see the PosgreSQL
community announcement (https://www.postgresql.org/about/news/1949/) and security x CVE-
2019-10164 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-10164) .
With this release, the pg_hint_plan extension has been updated to version 1.3.4.
For more information on the xes in PostgreSQL 11.4, see the PostgreSQL documentation
(https://www.postgresql.org/docs/11/release-11-4.html) .
PostgreSQL version 11.2 contains several bug xes for issues in release 11.1. For more
information on the xes in PostgreSQL 11.2, see the PostgreSQL documentation
This version also includes the following changes:

A new pgTAP (https://pgtap.org/) extension version 1.0.

Support for Amazon S3 import. For more information, see Importing Amazon S3 Data
into an RDS for PostgreSQL DB Instance
(PostgreSQL.Procedural.Importing.html#USER_PostgreSQL.S3Import) .
Multiple major version upgrade is available to PostgreSQL 11.2 from certain previous
PostgreSQL versions. For more information, see Major Version Upgrades for PostgreSQL
(USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion)
.
For information on upgrading the engine version for your PostgreSQL DB instance, see
Upgrading a PostgreSQL DB Instance
(CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.Patching) .
For the complete list of extensions supported by Amazon RDS for PostgreSQL, see Supported
PostgreSQL Features and Extensions
(CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeaturesExtensions) .
PostgreSQL version 11.1 contains several improvements that were announced in PostgreSQL
11.1 Released! (https://www.postgresql.org/about/news/1905/) This version includes SQL stored
procedures that enable embedded transactions within a procedure. This version also includes
major improvements to partitioning and parallelism and many useful performance
improvements. For example, by using a non-null constant for a column default, you can now
use an ALTER TABLE command to add a column without causing a table rewrite.
PostgreSQL version 11.1 contains several bug xes for issues in release 11. For complete
details, see the PostgreSQL Release 11.1 documentation
(https://www.postgresql.org/docs/11/release-11-1.html) . Some changes in this version include
the following:
Partitioning – Partitioning improvements include support for hash partitioning,

enabling creation of a default partition, and dynamic row movement to another
partition based on the key column update.
Performance – Performance improvements include parallelism while creating indexes,
materialized views, hash joins, and sequential scans to make the operations perform
better.
Stored procedures – SQL stored procedures now added support embedded transactions.
Support for Just-In-Time (JIT) capability – RDS PostgreSQL 11 instances are created
with JIT capability, speeding evaluation of expressions. To enable this feature, set jit to
ON.
Segment size – The write-ahead logging (WAL) segment size has been changed from 16
MB to 64 MB.
Autovacuum improvements – To provide valuable logging, the parameter
rds.force_autovacuum_logging is ON by default in conjunction with the
log_autovacuum_min_duration parameter set to 10 seconds. To increase autovacuum
e ectiveness, the values for the autovacuum_max_workers and
autovacuum_vacuum_cost_limit parameters are computed based on host memory
capacity to provide larger default values.
Improved transaction timeout – The parameter
idle_in_transaction_session_timeout is set to 12 hours. Any session that has been
idle more than 12 hours is terminated.
Performance metrics – The pg_stat_statements module is included in
shared_preload_libraries by default. This avoids having to reboot the instance
immediately after creation. However, this functionality still requires you to run the
statement CREATE EXTENSION pg_stat_statements;. Also, track_io_timing is
enabled by default to add more granular data to pg_stat_statements.
The tsearch2 module is no longer supported – If your application uses tsearch2
functions, update it to use the equivalent functions provided by the core PostgreSQL
engine. For more information about the tsearch2 module, see PostgreSQL tsearch2
(https://www.postgresql.org/docs/9.6/static/tsearch2.html) .
The chkpass module is no longer supported – For more information about the chkpass
module, see PostgreSQL chkpass (https://www.postgresql.org/docs/10/chkpass.html) .
Extension updates for RDS PostgreSQL 11.1 include the following:
pgaudit is updated to 1.3.0.
pg_hint_plan is updated to 1.3.2.
pglogical is updated to 2.2.1.
plcoffee is updated to 2.3.8.
plv8 is updated to 2.3.8.
PostGIS is updated to 2.5.1.
prefix is updated to 1.2.8.
wal2json is updated to hash 9e962bad.
PostgreSQL Version 11 on Amazon RDS in the Database Preview Environment
Note
PostgreSQL Version 11 on Amazon RDS has been released in the production

environment. It is no longer supported in the Database Preview Environment.
PostgreSQL version 11 contains several improvements that are described in PostgreSQL 11

Released! (https://www.postgresql.org/about/news/1894/)
This release contains an important security x and also bug xes and improvements done by
the PostgreSQL community. For more information on the security x, see the PosgreSQL
community announcement (https://www.postgresql.org/about/news/1949/) and security x CVE-
2019-10164 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-10164) .
For more information on the xes in PostgreSQL 10.9, see the PostgreSQL documentation
information on the xes in 10.7, see the PostgreSQL documentation
Support for Amazon S3 import. For more information, see Importing Amazon S3 Data
into an RDS for PostgreSQL DB Instance
(PostgreSQL.Procedural.Importing.html#USER_PostgreSQL.S3Import) .
Multiple major version upgrade is available to PostgreSQL 10.7 from certain previous
PostgreSQL versions. For more information, see Major Version Upgrades for PostgreSQL
(USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion)
.
information on the xes in PostgreSQL 10.6, see the PostgreSQL documentation
(http://www.postgresql.org/docs/10/static/release-10-6.html) .
A new rds.restrict_password_commands parameter and a new rds_password role

have been introduced. When the rds.restrict_password_commands parameter is
enabled, only users who have the rds_password role can make user password and
password expiration changes. By restricting password-related operations to a limited set
of roles, you can implement policies such as password complexity requirements from
the client side. The rds.restrict_password_commands parameter is static, so it
requires a database restart to change it. For more information, see Restricting Password
Management
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.RestrictPass
.
The logical decoding plugin wal2json has been updated to commit 9e962ba.
Note
Amazon RDS for PostgreSQL has announced the removal of the tsearch2
extension in the next major release. We encourage customers still using pre-8.3
text search to migrate to the equivalent built-in features. For more information
about migrating, see the PostgreSQL documentation
(https://www.postgresql.org/docs/9.6/static/textsearch-migration.html) .
Support for the pglogical extension version 2.2.0. Prerequisites for using this
extension are the same as the prerequisites for using logical replication for PostgreSQL
as described in Logical Replication for PostgreSQL on Amazon RDS
(CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.LogicalReplication) .
Support for the pg_similarity extension version 1.0.
Support for the pageinspect extension version 1.6.
Support for the libprotobuf extension version 1.3.0 for the PostGIS component.
An update for the pg_hint_plan extension to version 1.3.1.
An update for the wal2json extension to version 01c5c1e.
Support for PostgreSQL 10 Logical Replication using the native publication and
subscription framework. RDS PostgreSQL databases can function as both publishers and
subscribers. You can specify replication to other PostgreSQL databases at the database-
level or at the table-level. With logical replication, the publisher and subscriber
databases need not be physically identical (block-to-block) to each other. This allows for
use cases such as data consolidation, data distribution, and data replication across
di erent database versions for 10.4 and above. For more details, refer to Logical
Replication for PostgreSQL on Amazon RDS
The temporary le size limitation is user-con gurable. You require the rds_superuser
role to modify the temp_file_limit parameter.
Update of the GDAL library, which is used by the PostGIS extension. See Working with
PostGIS
.
Update of the ip4r extension to version 2.1.1.

Update of the pg_repack extension to version 1.4.3. See Working with the pg_repack
Extension
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.pg_repack)
.
Update of the plv8 extension to version 2.1.2.
Note
The tsearch2 extension is to be removed in the next major release. We
encourage customers still using pre-8.3 text search to migrate to the equivalent
built-in features. For more information about migrating, see the PostgreSQL
documentation (https://www.postgresql.org/docs/9.6/static/textsearch-migration.html)
.
PostgreSQL version 10.3 contains several bug xes for issues in release 10. For more
Version 2.1.0 of PL/v8 is now available. If you use PL/v8 and upgrade PostgreSQL to a new
PL/v8 version, you immediately take advantage of the new extension but the catalog
metadata doesn't re ect this fact. For the steps to synchronize your catalog metadata with
the new version of PL/v8, see Upgrade PL/v8
(CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.UpgradingPLv8) .
PostgreSQL version 10.1 contains several bug xes for issues in release 10. For more
(http://www.postgresql.org/docs/10/static/release-10-1.html) and the PostgreSQL 10 community
announcement (https://www.postgresql.org/about/news/1786/) .
PostgreSQL version 10.1 includes the following changes:
Declarative table partitioning – PostgreSQL 10 adds table partitioning to SQL syntax

and native tuple routing.
Parallel queries – When you create a new PostgreSQL 10.1 instance, parallel queries are
enabled for the default.postgres10 parameter group. The parameter
max_parallel_workers_per_gather (https://www.postgresql.org/docs/10/static/runtime-
con g-resource.html#GUC-MAX-PARALLEL-WORKERS-PER-GATHER) is set to 2 by default, but
you can modify it to support your speci c workload requirements.
Support for the International Components for Unicode (ICU) – You can use the ICU
library to provide explicitly versioned collations. Amazon RDS for PostgreSQL 10.1 is
compiled with ICU version 60.2. For more information about ICU implementation in
PostgreSQL, see Collation Support
(https://www.postgresql.org/docs/10/static/collation.html) .
Huge pages – Huge pages is a feature of the Linux kernel that uses multiple page size
capabilities of modern hardware architectures. Amazon RDS for PostgreSQL supports
huge pages with a global con guration parameter. When you create a new PostgreSQL
10.1 instance with RDS, the huge_pages parameter is set to "on" for the
default.postgres10 parameter group. You can modify this setting to support your
speci c workload requirements.
PL/v8 update – PL/v8 is a procedural language that allows you to write functions in
JavaScript that you can then call from SQL. This release of PostgreSQL supports version
2.1.0 of PL/v8.
Renaming of xlog and location – In PostgreSQL version 10 the abbreviation "xlog" has
changed to "wal", and the term "location" has changed to "lsn". For more information,
see https://www.postgresql.org/docs/10/static/release-10.html#id-1.11.6.8.4
(https://www.postgresql.org/docs/10/static/release-10.html#id-1.11.6.8.4) .
tsearch2 module – Amazon RDS continues to provide the tsearch2 module in
PostgreSQL version 10, but is to remove it in the next major version release. If your
application uses tsearch2 functions update it to use the equivalent functions the core
engine provides. For more information about using tsearch2, see tsearch2 module
(https://www.postgresql.org/docs/9.6/static/tsearch2.html) .
PostgreSQL Version 9.6.14 on Amazon RDS
This release contains bug xes and improvements done by the PostgreSQL community.
For more information on the xes in PostgreSQL 9.6.14, see the PostgreSQL documentation
(https://www.postgresql.org/docs/9.6/release-9-6-14.html) .
PostgreSQL version 9.6.12 contains several bug xes for issues in release 9.6.11. For more
information on the xes in 9.6.12, see the PostgreSQL documentation
(http://www.postgresql.org/docs/9.6/release-9-6-12.html) .
information on the xes in PostgreSQL 9.6.11, see the PostgreSQL documentation
(http://www.postgresql.org/docs/9.6/static/release-9-6-11.html) . For information on upgrading
the engine version for your PostgreSQL DB instance, see Upgrading a PostgreSQL DB Instance
With this version, the logical decoding plugin wal2json has been updated to commit
9e962ba.
(http://www.postgresql.org/docs/current/static/release-9-6-10.html) .
This version includes the following changes:
Support for the pglogical extension version 2.2.0. Prerequisites for using this
extension are the same as the prerequisites for using logical replication for PostgreSQL
as described in Logical Replication for PostgreSQL on Amazon RDS
Support for the pg_similarity extension version 2.2.0.
An update for the wal2json extension to version 01c5c1e.
An update for the pg_hint_plan extension to version 1.2.3.
(http://www.postgresql.org/docs/9.6/static/release-9-6-9.html) . For information on upgrading the
engine version for your PostgreSQL DB instance, see Upgrading a PostgreSQL DB Instance
This version includes the following changes:
The temporary le size limitation is user-con gurable. You require the rds_superuser
role to modify the temp_file_limit parameter.
Update of the GDAL library, which is used by the PostGIS extension. See Working with
PostGIS
.
Update of the ip4r extension to version 2.1.1.
Update of the pgaudit extension to version 1.1.1. See Working with the pgaudit
Extension
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.pgaudit)
.
Update of the pg_repack extension to version 1.4.3. See Working with the pg_repack
Extension
.
This version includes the following features:
Supports the orafce extension, version 3.6.1. This extension contains functions that are
native to commercial databases, and can be helpful if you are porting a commercial
database to PostgreSQL. For more information about using orafce with Amazon RDS,
see Working with the orafce Extension
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.orafce) .
Supports the prefix extension, version 1.2.6. This extension provides an operator for
text pre x searches. For more information about prefix, see the pre x project on
GitHub (https://github.com/dimitri/pre x) .
Supports version 2.3.4 of PostGIS, version 2.4.2 of pgrouting, and an updated version of
wal2json.
This version also includes support for the pgrouting (http://pgrouting.org/) and postgresql-hll
(https://github.com/citusdata/postgresql-hll/releases/tag/v2.10.2) extensions, and the decoder_raw
(https://github.com/michaelpq/pg_plugins/tree/master/decoder_raw) optional module.
PostgreSQL version 9.6.3 contains several new features and bug xes. This version includes
the following features:
Supports the extension pg_repack version 1.4.0. You can use this extension to remove
bloat from tables and indexes. For more information on using pg_repack with Amazon
RDS, see Working with the pg_repack Extension
.
Supports the extension pgaudit version 1.1.0. This extension provides detailed session
and object audit logging. For more information on using pgaudit with Amazon RDS, see
Working with the pgaudit Extension
.
Supports wal2json, an output plugin for logical decoding.
Supports the auto_explain module. You can use this module to log execution plans of
slow statements automatically. The following example shows how to use auto_explain
from within an Amazon RDS PostgreSQL session:
LOAD '$libdir/plugins/auto_explain';
For more information on using auto_explain, see the PostgreSQL documentation

(https://www.postgresql.org/docs/current/static/auto-explain.html) .
PostgreSQL version 9.6.2 contains several new features and bug xes. The new version also
includes the following extension versions:
PostGIS version 2.3.2

pg_freespacemap (https://www.postgresql.org/docs/current/static/pgfreespacemap.html)
version 1.1–Provides a way to examine the free space map (FSM). This extension
provides an overloaded function called pg_freespace. The functions show the value
recorded in the free space map for a given page, or for all pages in the relation.
pg_hint_plan (http://pghintplan.osdn.jp/pg_hint_plan.html) version 1.1.3– Provides control
of execution plans by using hinting phrases at the beginning of SQL statements.
log_fdw version 1.0–Using this extension from Amazon RDS, you can load and query
your database engine log from within the database. For more information, see Using the
log_fdw Extension (CHAP_PostgreSQL.html#CHAP_PostgreSQL.Extensions.log_fdw) .
With this version release, you can now edit the max_worker_processes parameter in a
DB parameter group.
PostgreSQL version 9.6.2 on Amazon RDS also supports altering enum values. For more
information, see ALTER ENUM for PostgreSQL
(CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.AlterEnum) .
For more information on the xes in 9.6.2, see the PostgreSQL documentation
PostgreSQL version 9.6.1 contains several new features and improvements. For more
information about the xes and improvements in PostgreSQL 9.6.1, see the PostgreSQL
documentation (https://www.postgresql.org/docs/9.6/static/release-9-6-1.html) . For information
on upgrading the engine version for your PostgreSQL DB instance, see Upgrading a
PostgreSQL DB Instance (CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.Patching) . For
information about performing parallel queries and phrase searching using Amazon RDS for
PostgreSQL 9.6.1, see the AWS Database Blog
(https://aws.amazon.com/blogs/database/performing-parallel-queries-and-phrase-searching-with-
amazon-rds-for-postgresql-9-6-1/) .
PostgreSQL version 9.6.1 includes the following changes:
Parallel query execution: Supports parallel execution of large read-only queries,

allowing sequential scans, hash joins, nested loops, and aggregates to be run in parallel.
By default, parallel query execution is not enabled. To enable parallel query execution,
set the parameter max_parallel_workers_per_gather to a value larger than zero.
Updated postgres_fdw extension: Supports remote JOINs, SORTs, UPDATEs, and

DELETE operations.
PL/v8 update: Provides version 1.5.3 of the PL/v8 language.
PostGIS version update: Supports POSTGIS="2.3.0 r15146" GEOS="3.5.0-CAPI-1.9.0
r4084" PROJ="Rel. 4.9.2, 08 September 2015" GDAL="GDAL 2.1.1, released
2016/07/07" LIBXML="2.9.1" LIBJSON="0.12" RASTER
Vacuum improvement: Avoids scanning pages unnecessarily during vacuum freeze

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

bloom, an index access method based on Bloom lters
(http://en.wikipedia.org/wiki/Bloom_ lter)
pg_visibility, which provides a means for examining the visibility map and
page-level visibility information of a table.
With the release of version 9.6.2, you can now edit the max_worker_processes
parameter in a PostgreSQL version 9.6.1 DB parameter group.
You can create a new PostgreSQL 9.6.1 database instance using the AWS Management
Console, AWS CLI, or RDS API. You can also upgrade an existing PostgreSQL 9.5 instance to
version 9.6.1 using major version upgrade. If you want to upgrade a DB instance from version
9.3 or 9.4 to 9.6, you must perform a point-and-click upgrade to the next major version rst.
Each upgrade operation involves a short period of unavailability for your DB instance.
This release contains bug xes and improvements done by the PostgreSQL community.
For more information on the xes in PostgreSQL 9.5.18, see the PostgreSQL documentation
(http://www.postgresql.org/docs/current/release-9-5-16.html) . For information on upgrading the
(http://www.postgresql.org/docs/current/static/release-9-5-15.html) . For information on
upgrading the engine version for your PostgreSQL DB instance, see Upgrading a PostgreSQL
DB Instance (CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.Patching) .
This version includes the following extension updates:
Update of the pgaudit extension to version 1.0.6. See Working with the pgaudit
Extension
.
Update of the pg_hint_plan extension to version 1.1.5.
PostgreSQL version 9.5.12 contains several bug xes for issues in release 9.5.10 For more
PostgreSQL version 9.5.10 contains several bug xes for issues in version 9.5.9. For more
PostgreSQL version 9.5.7 contains several new features and bug xes. This version includes
the following features:
Supports the extension pgaudit version 1.0.5. This extension provides detailed session
and object audit logging. For more information on using pgaudit with Amazon RDS, see
Working with the pgaudit Extension
.
Supports wal2json, an output plugin for logical decoding.
Supports the auto_explain module. You can use this module to log execution plans of
slow statements automatically. The following example shows how to use auto_explain
from within an Amazon RDS PostgreSQL session.
LOAD '$libdir/plugins/auto_explain';
For more information on using auto_explain, see the PostgreSQL documentation

(https://www.postgresql.org/docs/current/static/auto-explain.html) .
PostgreSQL version 9.5.6 contains several new features and bug xes. The new version also
includes the following extension versions:
PostGIS version 2.2.5

pg_freespacemap (https://www.postgresql.org/docs/current/static/pgfreespacemap.html)
version 1.1–Provides a way to examine the free space map (FSM). This extension
provides an overloaded function called pg_freespace. This function shows the value
recorded in the free space map for a given page, or for all pages in the relation.
pg_hint_plan (http://pghintplan.osdn.jp/pg_hint_plan.html) version 1.1.3– Provides control
of execution plans by using hinting phrases at the beginning of SQL statements.
PostgreSQL version 9.5.6 on Amazon RDS also supports altering enum values. For more
information, see ALTER ENUM for PostgreSQL
(CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.AlterEnum) .
PostgreSQL version 9.5.4 contains several xes to issue found in previous versions. For more
Beginning with PostgreSQL version 9.4, PostgreSQL supports the streaming of WAL changes
using logical replication decoding. Amazon RDS supports logical replication for PostgreSQL
version 9.4.9 and higher and 9.5.4 and higher. For more information about PostgreSQL logical
replication on Amazon RDS, see Logical Replication for PostgreSQL on Amazon RDS
Beginning with PostgreSQL version 9.5.4 for Amazon RDS, the command ALTER USER WITH
BYPASSRLS is supported.
PostgreSQL versions 9.4.9 and later and version 9.5.4 and later support event triggers, and
Amazon RDS supports event triggers for these versions. You can use the master user account
can be used to create, modify, rename, and delete event triggers. Event triggers are at the DB
instance level, so they can apply to all databases on an instance. For more information about
PostgreSQL event triggers on Amazon RDS, see Event Triggers for PostgreSQL on Amazon
RDS (CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.EventTriggers) .
PostgreSQL version 9.5.2 contains several xes to issues found in previous versions. For more
information on the features in 9.5.2, see the PostgreSQL documentation
(http://www.postgresql.org/docs/9.5/static/release-9-5.html) . For information on upgrading the
PostgreSQL version 9.5.2 doesn't support the db.m1 or db.m2 DB instance classes. If you
need to upgrade a DB instance running PostgreSQL version 9.4 to version 9.5.2 to one of
these instance classes, you need to scale compute. To do that, you need a comparable db.t2
or db.m3 DB instance class before you can upgrade a DB instance running PostgreSQL version
9.4 to version 9.5.2. For more information on DB instance classes, see Choosing the DB
Instance Class (Concepts.DBInstanceClass.html) .
Native PostgreSQL version 9.5.2 introduced the command ALTER USER WITH BYPASSRLS.
This release includes updates from previous versions, including the following:
CVE-2016-2193: Fixes an issue where a query plan might be reused for more than one
ROLE in the same session. Reusing a query plan can cause the query to use the wrong
set of Row Level Security (RLS) policies.
CVE-2016-3065: Fixes a server crash bug triggered by using pageinspect with BRIN
index pages. Because an attacker might be able to expose a few bytes of server
memory, this crash is being treated as a security issue.
Major enhancements in RDS PostgreSQL 9.5 include the following:
UPSERT: Allow INSERTs that would generate constraint con icts to be turned into
UPDATEs or ignored
Add the GROUP BY analysis features GROUPING SETS, CUBE, and ROLLUP
Add row-level security control
Create mechanisms for tracking the progress of replication, including methods for
identifying the origin of individual changes during logical replication
Add Block Range Indexes (BRIN)
Add substantial performance improvements for sorting
Add substantial performance improvements for multi-CPU machines
PostGIS 2.2.2 - To use this latest version of PostGIS, use the ALTER EXTENSION UPDATE
statement to update after you upgrade to version 9.5.2. Example:
ALTER EXTENSION POSTGIS UPDATE TO '2.2.2'
Improved visibility of autovacuum sessions by allowing the rds_superuser account to
view autovacuum sessions in pg_stat_activity. For example, you can identify and
terminate an autovacuum session that is blocking a command from running, or
executing slower than a manually issued vacuum command.
RDS PostgreSQL version 9.5.2 includes the following new extensions:
address_standardizer – A single-line address parser that takes an input address and

normalizes it based on a set of rules stored in a table, helper lex, and gaz tables.
hstore_plperl (http://www.postgresql.org/docs/current/static/hstore.html) – Provides
transforms for the hstore type for PL/Perl.
tsm_system_rows (http://www.postgresql.org/docs/current/static/tsm-system-rows.html) –
Provides the table sampling method SYSTEM_ROWS, which can be used in the
TABLESAMPLE clause of a SELECT command.

tsm_system_time (http://www.postgresql.org/docs/current/static/tsm-system-time.html) –
Provides the table sampling method SYSTEM_TIME, which can be used in the
TABLESAMPLE clause of a SELECT command.
This release contains bug xes and improvements done by the PostgreSQL community. For
more information on the xes in PostgreSQL 9.4.23, see the PostgreSQL documentation
information on the xes in 9.4.21, the PostgreSQL documentation
(http://www.postgresql.org/docs/current/release-9-4-21.html) . For information on upgrading the
information on the xes in 9.4.20, the PostgreSQL documentation
(http://www.postgresql.org/docs/current/static/release-9-4-20.html) . For information on
upgrading the engine version for your PostgreSQL DB instance, see Upgrading a PostgreSQL
DB Instance (CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.Patching) .
The plv8 extension has been updated to version 2.1.2. For the complete list of extensions
supported by Amazon RDS for PostgreSQL, see Supported PostgreSQL Features and
Extensions (CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeaturesExtensions) .
PostgreSQL version 9.4.12 contains several xes to issue found in previous versions.
PostgreSQL version 9.4.11 contains several xes to issue found in previous versions.
Amazon RDS supports event triggers for these versions. The master user account can be used
to create, modify, rename, and delete event triggers. Event triggers are at the DB instance
level, so they can apply to all databases on an instance. For more information about
level, so they can apply to all databases on an instance. For more information about
PostgreSQL version 9.4.7 includes improved visibility of autovacuum sessions by allowing the
rds_superuser account to view autovacuum sessions in pg_stat_activity. For example, you can
identify and terminate an autovacuum session that is blocking a command from running, or
executing slower than a manually issued vacuum command.
Note
Amazon RDS for PostgreSQL announced retirement of PostgreSQL 9.3 in
September 2018 and has stopped support for PostgreSQL version 9.3. We
encourage you to upgrade to PostgreSQL 9.4 or a higher version as early as
possible. For information on upgrading the engine version for your PostgreSQL
DB instance, see Upgrading a PostgreSQL DB Instance
Note
Amazon RDS for PostgreSQL has deprecated PostgreSQL version 9.3.x.
The plv8 extension has been updated to version 2.1.2. For the complete list of extensions
supported by Amazon RDS for PostgreSQL, see Supported PostgreSQL Features and
Extensions (CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeaturesExtensions) .
Note
Amazon RDS for PostgreSQL has announced version 9.3.x is scheduled for
retirement in September, 2018. We encourage you to upgrade your 9.3.x
databases to the latest version at your earliest convenience.

PostgreSQL version 9.3.17 contains several xes for bugs found in previous versions. This
version contains the same extension components as version 9.3.16. For a list of xes in
version 9.3.17, see the PostgreSQL documentation
PostgreSQL version 9.3.16 contains several xes for bugs found in previous versions. This
version contains the same extension components as version 9.3.14. For a list of xes in
version 9.3.16, see the PostgreSQL documentation
PostgreSQL version 9.3.14 contains several xes for bugs found in previous versions. For a list
of xes in version 9.3.14, see the PostgreSQL documentation
PostgreSQL version 9.3.12 contains several xes for bugs found in previous versions. For a list
of xes in version 9.3.12, see the PostgreSQL documentation
PostgreSQL version 9.3.12 includes improved visibility of autovacuum sessions by allowing

the rds_superuser account to view autovacuum sessions in pg_stat_activity. For example, you
can identify and terminate an autovacuum session that is blocking a command from running,
or executing slower than a manually issued vacuum command.
Supported PostgreSQL Features and Extensions
Amazon RDS supports many of the most common PostgreSQL extensions and features.
Topics
PostgreSQL Extensions and Modules Supported on Amazon RDS

(#PostgreSQL.Concepts.General.FeatureSupport.Extensions)
Upgrade PL/v8 (#PostgreSQL.Concepts.General.UpgradingPLv8)
Supported PostgreSQL Features (#PostgreSQL.Concepts.General.FeatureSupport)
Limits for PostgreSQL DB Instances (#PostgreSQL.Concepts.General.Limits)
Upgrading a PostgreSQL DB Instance (#PostgreSQL.Concepts.General.Patching)
Using SSL with a PostgreSQL DB Instance (#PostgreSQL.Concepts.General.SSL)
PostgreSQL Extensions and Modules Supported on Amazon RDS
PostgreSQL supports many PostgreSQL extensions and modules. Extensions and modules
expand on the functionality provided by the PostgreSQL engine. The following sections show
the extensions and modules supported by Amazon RDS for the major PostgreSQL versions.
Topics
PostgreSQL Version 12.x Extensions and Modules Supported on Amazon RDS in the
Database Preview Environment
(#PostgreSQL.Concepts.General.FeatureSupport.Extensions.12x)
PostgreSQL Version 11.x Extensions and Modules Supported on Amazon RDS
PostgreSQL Version 9.6.x Extensions and Modules Supported on Amazon RDS
PostgreSQL Version 9.5.x Extensions Supported on Amazon RDS
PostgreSQL Extension Support for PostGIS on Amazon RDS
(#CHAP_PostgreSQL.Extensions.SupportedPerVersion)
Using the log_fdw Extension (#CHAP_PostgreSQL.Extensions.log_fdw)
You can nd a list of extensions supported by Amazon RDS in the default DB parameter
group for that PostgreSQL version. You can also see the current extensions list using psql by
showing the rds.extensions parameter as in the following example.
SHOW rds.extensions;
Note
Parameters added in a minor version release might display inaccurately when
using the rds.extensions parameter in psql.
PostgreSQL Version 12.x Extensions and Modules Supported on Amazon RDS in the
Database Preview Environment
The following table shows PostgreSQL extensions and modules for PostgreSQL version 12.x
that are currently supported by PostgreSQL in the Amazon RDS Preview Environment. For
more information on PostgreSQL extensions, see Packaging Related Objects into an
Extension (https://www.postgresql.org/docs/12/static/extend-extensions.html) .
Extension Version 12
Beta 3
address_standardizer (http://postgis.net/docs/Address_Standardizer.html) 3.0.0alpha3
address_standardizer_data_us 3.0.0alpha3
(http://postgis.net/docs/Address_Standardizer.html)
bloom (https://www.postgresql.org/docs/12/bloom.html) 1.0

btree_gin (http://www.postgresql.org/docs/12/btree-gin.html) 1.3
btree_gist (http://www.postgresql.org/docs/12/btree-gist.html) 1.5
citext (http://www.postgresql.org/docs/12/citext.html) 1.6
cube (http://www.postgresql.org/docs/12/cube.html) 1.4
dblink (http://www.postgresql.org/docs/12/dblink.html) 1.2
dict_int (http://www.postgresql.org/docs/12/dict-int.html) 1.0
dict_xsyn (https://www.postgresql.org/docs/12/dict-xsyn.html) 1.0
earthdistance (http://www.postgresql.org/docs/12/earthdistance.html) 1.1
fuzzystrmatch (http://www.postgresql.org/docs/12/fuzzystrmatch.html) 1.1
hstore (http://www.postgresql.org/docs/12/hstore.html) 1.6
hstore_plperl (https://www.postgresql.org/docs/12/hstore.html) 1.0
intagg (http://www.postgresql.org/docs/12/intagg.html) 1.1
intarray (http://www.postgresql.org/docs/12/intarray.html) 1.2
ip4r (https://github.com/RhodiumToad/ip4r) 2.2
isn (http://www.postgresql.org/docs/12/isn.html) 1.2
jsonb_plperl 1.0
log_fdw—see Using the log_fdw Extension 1.1
(CHAP_PostgreSQL.html#CHAP_PostgreSQL.Extensions.log_fdw)
ltree (http://www.postgresql.org/docs/12/ltree.html) 1.1

pageinspect 1.7
pg_bu ercache (http://www.postgresql.org/docs/12/pgbu ercache.html) 1.3
pg_freespacemap (https://www.postgresql.org/docs/12/pgfreespacemap.html) 1.2
pg_prewarm (https://www.postgresql.org/docs/12/pgprewarm.html) 1.2
pg_similarity 1.0
pg_stat_statements (http://www.postgresql.org/docs/12/pgstatstatements.html) 1.7
pg_trgm (http://www.postgresql.org/docs/12/pgtrgm.html) 1.4
pg_visibility (https://www.postgresql.org/docs/12/pgvisibility.html) 1.2
pgcrypto (http://www.postgresql.org/docs/12/pgcrypto.html) 1.3
pgrouting (http://docs.pgrouting.org/2.3/en/doc/index.html) 2.6.1
pgrowlocks (http://www.postgresql.org/docs/12/pgrowlocks.html) 1.2

pgstattuple (http://www.postgresql.org/docs/12/pgstattuple.html) 1.5
pgTAP (https://pgtap.org/) 1.0.0
plperl (https://www.postgresql.org/docs/12/plperl.html) 1.0
plpgsql (https://www.postgresql.org/docs/12/plpgsql.html) 1.0
pltcl (https://www.postgresql.org/docs/12/pltcl-overview.html) 1.0
PostGIS (http://www.postgis.net/) 3.0.0alpha3
postgis_tiger_geocoder (http://postgis.net/docs/Geocode.html) 3.0.0alpha3
postgis_topology (http://postgis.net/docs/manual-dev/Topology.html) 3.0.0alpha3
postgres_fdw (http://www.postgresql.org/docs/12/postgres-fdw.html) 1.0
pre x (https://github.com/dimitri/pre x) 1.2.0
sslinfo (http://www.postgresql.org/docs/12/sslinfo.html) 1.2
tablefunc (http://www.postgresql.org/docs/12/tablefunc.html) 1.0
test_parser (https://www.postgresql.org/docs/9.4/static/test-parser.html) 1.0
tsm_system_rows (https://www.postgresql.org/docs/12/tsm-system-rows.html) 1.0
tsm_system_time (https://www.postgresql.org/docs/12/tsm-system-time.html) 1.0
unaccent (http://www.postgresql.org/docs/12/unaccent.html) 1.1
uuid-ossp (http://www.postgresql.org/docs/12/uuid-ossp.html) 1.1
The following tables show PostgreSQL extensions and modules for PostgreSQL version 11.x
that are currently supported by PostgreSQL on Amazon RDS. "N/A" indicates that the
extension or module is not available for that PostgreSQL version. For more information on
PostgreSQL extensions, see Packaging Related Objects into an Extension
(https://www.postgresql.org/docs/11/static/extend-extensions.html) .
Extension Version Version Version

11.1 11.2 11.4
address_standardizer 2.4.2 2.4.2 2.4.2
address_standardizer_data_us 2.4.2 2.4.2 2.4.2

bloom (https://www.postgresql.org/docs/10/static/bloom.html) 1.0 1.0 1.0

btree_gin (http://www.postgresql.org/docs/10/static/btree-gin.html) 1.2 1.2 1.2
btree_gist (http://www.postgresql.org/docs/10/static/btree- 1.5 1.5 1.5

gist.html)
citext (http://www.postgresql.org/docs/10/static/citext.html) 1.4 1.4 1.4

cube (http://www.postgresql.org/docs/10/static/cube.html) 1.2 1.2 1.2
dblink (http://www.postgresql.org/docs/10/static/dblink.html) 1.2 1.2 1.2
dict_int (http://www.postgresql.org/docs/10/static/dict-int.html) 1.0 1.0 1.0
dict_xsyn (https://www.postgresql.org/docs/10/static/dict-xsyn.html) 1.0 1.0 1.0
earthdistance 1.1 1.1 1.1
(http://www.postgresql.org/docs/10/static/earthdistance.html)
fuzzystrmatch 1.1 1.1 1.1

(http://www.postgresql.org/docs/10/static/fuzzystrmatch.html)
hstore (http://www.postgresql.org/docs/10/static/hstore.html) 1.4 1.4 1.4

hstore_plperl 1.0 1.0 1.0
(https://www.postgresql.org/docs/10/static/hstore.html)
intagg (http://www.postgresql.org/docs/10/static/intagg.html) 1.1 1.1 1.1

intarray (http://www.postgresql.org/docs/10/static/intarray.html) 1.2 1.2 1.2
ip4r (https://github.com/RhodiumToad/ip4r) 2.3 2.3 2.3
isn (http://www.postgresql.org/docs/10/static/isn.html) 1.1 1.1 1.1
log_fdw—see Using the log_fdw Extension 1.0 1.0 1.0
libprotobuf 1.3.0 1.3.0 1.3.0

ltree (http://www.postgresql.org/docs/10/static/ltree.html) 1.1 1.1 1.1
orafce (https://github.com/orafce/orafce) 3.6.1 3.6.1 3.6.1
pgaudit 1.3.0 1.3.0 1.3.0
(https://github.com/pgaudit/pgaudit/blob/master/README.md)
pg_bu ercache 1.3 1.3 1.3

(http://www.postgresql.org/docs/10/static/pgbu ercache.html)
pg_freespacemap 1.2 1.2 1.2

(https://www.postgresql.org/docs/10/static/pgfreespacemap.html)
pg_hint_plan (http://pghintplan.osdn.jp/pg_hint_plan.html) 1.3.2 1.3.2 1.3.4

pg_prewarm 1.1 1.1 1.1
(https://www.postgresql.org/docs/10/static/pgprewarm.html)
pg_repack (http://reorg.github.io/pg_repack/) 1.4.4 1.4.4 1.4.4

pg_similarity 1.0 1.0 1.0
pg_stat_statements 1.5 1.5 1.5
(http://www.postgresql.org/docs/10/static/pgstatstatements.html)
pg_trgm (http://www.postgresql.org/docs/10/static/pgtrgm.html) 1.3 1.3 1.3

pg_visibility 1.2 1.2 1.2
(https://www.postgresql.org/docs/10/static/pgvisibility.html)
pgcrypto (http://www.postgresql.org/docs/10/static/pgcrypto.html) 1.3 1.3 1.3

pageinspect 1.6 1.6 1.6
pglogical 2.2.1 2.2.1 2.2.1
pgrowlocks 1.2 1.2 1.2
(http://www.postgresql.org/docs/10/static/pgrowlocks.html)
pgrouting (http://docs.pgrouting.org/2.3/en/doc/index.html) 2.6.1 2.6.1 2.6.1

pgstattuple 1.5 1.5 1.5
(http://www.postgresql.org/docs/10/static/pgstattuple.html)
pgTAP (https://pgtap.org/) NA 1.0 1.0

plco ee 2.3.8 2.3.8 2.3.8
plls 2.3.8 2.3.8 2.3.8
plperl (https://www.postgresql.org/docs/10/static/plperl.html) 1.0 1.0 1.0
plpgsql (https://www.postgresql.org/docs/10/static/plpgsql.html) 1.0 1.0 1.0
pltcl (https://www.postgresql.org/docs/10/static/pltcl-overview.html) 1.0 1.0 1.0
plv8 (https://github.com/plv8) 2.3.8 2.3.8 2.3.8
PostGIS (http://www.postgis.net/) 2.5.1 2.5.1 2.5.1
postgis_tiger_geocoder (http://postgis.net/docs/Geocode.html) 2.5.1 2.5.1 2.5.1
postgis_topology (http://postgis.net/docs/manual- 2.5.0 2.5.0 2.5.0
dev/Topology.html)
postgres_fdw (http://www.postgresql.org/docs/10/static/postgres- 1.0 1.0 1.0

fdw.html)
postgresql-hll (https://github.com/citusdata/postgresql- 2.11 2.11 2.11

hll/releases/tag/v2.10.2)
pre x (https://github.com/dimitri/pre x) 1.2.8 1.2.8 1.2.8

sslinfo (http://www.postgresql.org/docs/10/static/sslinfo.html) 1.2 1.2 1.2
tablefunc (http://www.postgresql.org/docs/10/static/tablefunc.html) 1.0 1.0 1.0
test_parser (https://www.postgresql.org/docs/9.4/static/test- 1.0 1.0 1.0
parser.html)
tsm_system_rows (https://www.postgresql.org/docs/10/static/tsm- 1.0 1.0 1.0

system-rows.html)
tsm_system_time (https://www.postgresql.org/docs/10/static/tsm- 1.0 1.0 1.0

system-time.html)
unaccent (http://www.postgresql.org/docs/10/static/unaccent.html) 1.1 1.1 1.1

uuid-ossp (http://www.postgresql.org/docs/10/static/uuid- 1.1 1.1 1.1
ossp.html)
The following modules are supported as shown for PostgreSQL version 11.x.
Module Version 11.1 Version 11.2 Version 11.4

amcheck Supported Supported Supported
auto_explain Supported Supported Supported
decoder_raw Supported Supported Supported
ICU Version 60.2 supported Version 60.2 supported Version 60.2 supported
test_decoding Supported Supported Supported
wal2json Commit hash 9e962bad Commit hash 9e962bad Commit hash 9e962bad
The following tables show PostgreSQL extensions and modules for PostgreSQL version 10
(https://www.postgresql.org/docs/9.6/static/extend-extensions.html) .
Extension 10.1 10.3 10.4 10.5

address_standardizer 2.4.2 2.4.2 2.4.2 2.4.2
address_standardizer_data_us 2.4.2 2.4.2 2.4.2 2.4.2

bloom (https://www.postgresql.org/docs/10/static/bloom.html) 1.0 1.0 1.0 1.0

btree_gin (http://www.postgresql.org/docs/10/static/btree- 1.2 1.2 1.2 1.2
gin.html)
btree_gist (http://www.postgresql.org/docs/10/static/btree- 1.5 1.5 1.5 1.5

gist.html)
chkpass (http://www.postgresql.org/docs/10/static/chkpass.html) 1.0 1.0 1.0 1.0

citext (http://www.postgresql.org/docs/10/static/citext.html) 1.4 1.4 1.4 1.4
cube (http://www.postgresql.org/docs/10/static/cube.html) 1.2 1.2 1.2 1.2
dblink (http://www.postgresql.org/docs/10/static/dblink.html) 1.2 1.2 1.2 1.2
dict_int (http://www.postgresql.org/docs/10/static/dict-int.html) 1.0 1.0 1.0 1.0

dict_xsyn (https://www.postgresql.org/docs/10/static/dict- 1.0 1.0 1.0 1.0
xsyn.html)
earthdistance 1.1 1.1 1.1 1.1

(http://www.postgresql.org/docs/10/static/earthdistance.html)
fuzzystrmatch 1.1 1.1 1.1 1.1

(http://www.postgresql.org/docs/10/static/fuzzystrmatch.html)
hstore (http://www.postgresql.org/docs/10/static/hstore.html) 1.4 1.4 1.4 1.4

hstore_plperl 1.0 1.0 1.0 1.0
(https://www.postgresql.org/docs/10/static/hstore.html)
intagg (http://www.postgresql.org/docs/10/static/intagg.html) 1.1 1.1 1.1 1.1

intarray (http://www.postgresql.org/docs/10/static/intarray.html) 1.2 1.2 1.2 1.2
ip4r (https://github.com/RhodiumToad/ip4r) 2.0 2.0 2.1.1 2.1.1
isn (http://www.postgresql.org/docs/10/static/isn.html) 1.1 1.1 1.1 1.1
log_fdw—see Using the log_fdw Extension 1.0 1.0 1.0 1.0
libprotobuf N/A N/A N/A 1.3.0

ltree (http://www.postgresql.org/docs/10/static/ltree.html) 1.1 1.1 1.1 1.1
orafce (https://github.com/orafce/orafce) 3.6.1 3.6.1 3.6.1 3.6.1
pgaudit 1.2.0 1.2.0 1.2.0 1.2.0
pg_bu ercache 1.3 1.3 1.3 1.3

(http://www.postgresql.org/docs/10/static/pgbu ercache.html)
pg_freespacemap 1.2 1.2 1.2 1.2

(https://www.postgresql.org/docs/10/static/pgfreespacemap.html)
pg_hint_plan (http://pghintplan.osdn.jp/pg_hint_plan.html) 1.3.0 1.3.0 1.3.0 1.3.1

pg_prewarm 1.1 1.1 1.1 1.1
(https://www.postgresql.org/docs/10/static/pgprewarm.html)
pg_repack (http://reorg.github.io/pg_repack/) 1.4.2 1.4.2 1.4.3 1.4.3

pg_similarity N/A N/A N/A 1.0
pg_stat_statements 1.5 1.5 1.5 1.5
(http://www.postgresql.org/docs/10/static/pgstatstatements.html)
pg_trgm (http://www.postgresql.org/docs/10/static/pgtrgm.html) 1.3 1.3 1.3 1.3

pg_visibility 1.2 1.2 1.2 1.2
(https://www.postgresql.org/docs/10/static/pgvisibility.html)
pgcrypto 1.3 1.3 1.3 1.3

(http://www.postgresql.org/docs/10/static/pgcrypto.html)
pageinspect N/A N/A N/A 1.6

pglogical N/A N/A N/A 2.2.0
pgrowlocks 1.2 1.2 1.2 1.2
(http://www.postgresql.org/docs/10/static/pgrowlocks.html)
pgrouting (http://docs.pgrouting.org/2.3/en/doc/index.html) 2.5.2 2.5.2 2.5.2 2.5.2

pgstattuple 1.5 1.5 1.5 1.5
(http://www.postgresql.org/docs/10/static/pgstattuple.html)
plco ee 2.1.0 2.1.0 2.1.2 2.1.2

plls 2.1.0 2.1.0 2.1.2 2.1.2
plperl (https://www.postgresql.org/docs/10/static/plperl.html) 1.0 1.0 1.0 1.0
plpgsql (https://www.postgresql.org/docs/10/static/plpgsql.html) 1.0 1.0 1.0 1.0
pltcl (https://www.postgresql.org/docs/10/static/pltcl- 1.0 1.0 1.0 1.0
overview.html)
plv8 (https://github.com/plv8) 2.1.0 2.1.0 2.1.2 2.1.2

PostGIS (http://www.postgis.net/) 2.4.2 2.4.2 2.4.4 2.4.4
postgis_tiger_geocoder (http://postgis.net/docs/Geocode.html) 2.4.2 2.4.2 2.4.2 2.4.2
postgis_topology (http://postgis.net/docs/manual- 2.4.2 2.4.2 2.4.2 2.4.2
dev/Topology.html)
postgres_fdw 1.0 1.0 1.0 1.0

(http://www.postgresql.org/docs/10/static/postgres-fdw.html)
postgresql-hll (https://github.com/citusdata/postgresql- 2.10.2 2.10.2 2.10.2 2.10.2

pre x (https://github.com/dimitri/pre x) 1.2.0 1.2.0 1.2.0 1.2.0

sslinfo (http://www.postgresql.org/docs/10/static/sslinfo.html) 1.2 1.2 1.2 1.2
tablefunc 1.0 1.0 1.0 1.0
(http://www.postgresql.org/docs/10/static/tablefunc.html)
test_parser (https://www.postgresql.org/docs/9.4/static/test- 1.0 1.0 1.0 1.0

parser.html)
tsearch2 1.0 1.0 1.0 1.0

(http://www.postgresql.org/docs/9.6/static/tsearch2.html)
(deprecated in version 10)
tsm_system_rows 1.0 1.0 1.0 1.0
(https://www.postgresql.org/docs/10/static/tsm-system-
rows.html)
tsm_system_time 1.0 1.0 1.0 1.0

(https://www.postgresql.org/docs/10/static/tsm-system-
time.html)
unaccent 1.1 1.1 1.1 1.1

(http://www.postgresql.org/docs/10/static/unaccent.html)
uuid-ossp (http://www.postgresql.org/docs/10/static/uuid- 1.1 1.1 1.1 1.1

ossp.html)
The tsearch2 extension is deprecated in version 10. The PostgreSQL team plans to remove
tsearch2 from the next major release of PostgreSQL.
The following modules are supported as shown for versions of PostgreSQL 10.
Module Version 10.3 10.4 10.5 10.6 10.7 10.9

10.1
amcheck Not Supported Supported Supported Supported Supported Sup
Supported
auto_explain Supported Supported Supported Supported Supported Supported Sup
decoder_raw Supported Supported Supported Supported Supported Supported Sup
ICU Version Version Version Version Version Version Vers
60.2 60.2 60.2 60.2 60.2 60.2 60.2
supported supported supported supported supported supported sup
test_decoding Supported Supported Supported Supported Supported Supported Sup
wal2json Commit Commit Commit Commit Commit Commit Com
hash hash hash hash hash hash has
5352cc4 5352cc4 5352cc4 01c5c1e 9e962ba 9e962ba 9e9
The following tables show PostgreSQL extensions and modules for PostgreSQL version 9.6.x
Extension 9.6.1 9.6.2 9.6.3 9.6.5


bloom (https://www.postgresql.org/docs/9.6/static/bloom.html) 1.0 1.0 1.0 1.0
btree_gin (http://www.postgresql.org/docs/9.6/static/btree-gin.html) 1.0 1.0 1.0 1.0

btree_gist (http://www.postgresql.org/docs/9.6/static/btree- 1.2 1.2 1.2 1.2
gist.html)
chkpass (http://www.postgresql.org/docs/9.6/static/chkpass.html) 1.0 1.0 1.0 1.0

citext (http://www.postgresql.org/docs/9.6/static/citext.html) 1.3 1.3 1.3 1.3
cube (http://www.postgresql.org/docs/9.6/static/cube.html) 1.2 1.2 1.2 1.2
dblink (http://www.postgresql.org/docs/9.6/static/dblink.html) 1.2 1.2 1.2 1.2
dict_int (http://www.postgresql.org/docs/9.6/static/dict-int.html) 1.0 1.0 1.0 1.0
dict_xsyn (https://www.postgresql.org/docs/9.6/static/dict-xsyn.html) 1.0 1.0 1.0 1.0
(http://www.postgresql.org/docs/9.6/static/earthdistance.html)

(http://www.postgresql.org/docs/9.6/static/fuzzystrmatch.html)
hstore (http://www.postgresql.org/docs/9.6/static/hstore.html) 1.4 1.4 1.4 1.4

(https://www.postgresql.org/docs/9.6/static/hstore.html)
intagg (http://www.postgresql.org/docs/9.6/static/intagg.html) 1.1 1.1 1.1 1.1

intarray (http://www.postgresql.org/docs/9.6/static/intarray.html) 1.2 1.2 1.2 1.2
ip4r (https://github.com/RhodiumToad/ip4r) 2.0 2.0 2.0 2.0
isn (http://www.postgresql.org/docs/9.6/static/isn.html) 1.1 1.1 1.1 1.1
log_fdw—see Using the log_fdw Extension N/A 1.0 1.0 1.0
ltree (http://www.postgresql.org/docs/9.6/static/ltree.html) 1.1 1.1 1.1 1.1

orafce (https://github.com/orafce/orafce) N/A N/A N/A N/A
pgaudit N/A N/A 1.1 1.1
pg_bu ercache 1.2 1.2 1.2 1.2

(http://www.postgresql.org/docs/9.6/static/pgbu ercache.html)
pg_freespacemap N/A 1.1 1.1 1.1

(https://www.postgresql.org/docs/current/static/pgfreespacemap.html)
pg_hint_plan (http://pghintplan.osdn.jp/pg_hint_plan.html) N/A 1.1.3 1.1.3 1.1.3

pg_prewarm 1.1 1.1 1.1 1.1
(https://www.postgresql.org/docs/9.6/static/pgprewarm.html)
pg_repack (http://reorg.github.io/pg_repack/) N/A N/A 1.4.0 1.4.1

pg_similarity N/A N/A N/A N/A
(http://www.postgresql.org/docs/9.6/static/pgstatstatements.html)
pg_trgm (http://www.postgresql.org/docs/9.6/static/pgtrgm.html) 1.3 1.3 1.3 1.3

pg_visibility 1.1 1.1 1.1 1.1
(https://www.postgresql.org/docs/9.6/static/pgvisibility.html)
pgcrypto (http://www.postgresql.org/docs/9.6/static/pgcrypto.html) 1.3 1.3 1.3 1.3

pglogical N/A N/A N/A N/A
pgrowlocks 1.2 1.2 1.2 1.2
(http://www.postgresql.org/docs/9.6/static/pgrowlocks.html)
pgrouting (http://docs.pgrouting.org/2.3/en/doc/index.html) N/A N/A N/A 2.3.2

(http://www.postgresql.org/docs/9.6/static/pgstattuple.html)
plco ee 1.5.3 1.5.3 1.5.3 1.5.3

plls 1.5.3 1.5.3 1.5.3 1.5.3
plperl (https://www.postgresql.org/docs/current/static/plperl.html) 1.0 1.0 1.0 1.0
plpgsql (https://www.postgresql.org/docs/current/static/plpgsql.html) 1.0 1.0 1.0 1.0
pltcl (https://www.postgresql.org/docs/current/static/pltcl- 1.0 1.0 1.0 1.0
overview.html)

dev/Topology.html)
postgres_fdw (http://www.postgresql.org/docs/9.6/static/postgres- 1.0 1.0 1.0 1.0

fdw.html)
postgresql-hll (https://github.com/citusdata/postgresql- N/A N/A N/A 2.10.2

pre x (https://github.com/dimitri/pre x) N/A N/A N/A N/A

sslinfo (http://www.postgresql.org/docs/9.6/static/sslinfo.html) 1.2 1.2 1.2 1.2
tablefunc (http://www.postgresql.org/docs/9.6/static/tablefunc.html) 1.0 1.0 1.0 1.0
parser.html)
tsearch2 (http://www.postgresql.org/docs/9.6/static/tsearch2.html) 1.0 1.0 1.0 1.0

tsm_system_rows 1.0 1.0 1.0 1.0
(https://www.postgresql.org/docs/current/static/tsm-system-
rows.html)
tsm_system_time 1.0 1.0 1.0 1.0

time.html)
unaccent (http://www.postgresql.org/docs/9.6/static/unaccent.html) 1.1 1.1 1.1 1.1

uuid-ossp (http://www.postgresql.org/docs/9.6/static/uuid-ossp.html) 1.1 1.1 1.1 1.1
The following modules are supported as shown for versions of PostgreSQL 9.6.
Module 9.6.1 9.6.2 9.6.3 9.6.5 9.6.8 9.6.9 9.6.

auto_explain N/A N/A Supported Supported Supported Supported Sup
decoder_raw N/A N/A N/A Supported Supported Supported Sup
test_decoding Supported Supported Supported Supported Supported Supported Sup
wal2json N/A N/a Commit Commit Commit Commit Com
hash hash hash hash has
2828409 645ab69 5352cc4 5352cc4 01c
The following tables show PostgreSQL extensions and modules for PostgreSQL version 9.5.x
Extension 9.5.2 9.5.4 9.5.6 9.5.7


bloom (https://www.postgresql.org/docs/9.6/static/bloom.html) N/A N/A N/A N/A

gist.html)





log_fdw—see Using the log_fdw Extension N/A N/A N/A N/A

pgaudit N/A N/A N/A 1.0.5
pg_bu ercache 1.1 1.1 1.1 1.1

pg_freespacemap N/A N/A 1.0 1.0

pg_hint_plan (http://pghintplan.osdn.jp/pg_hint_plan.html) N/A N/A 1.1.3 1.1.3

pg_prewarm 1.0 1.0 1.0 1.0


pg_visibility N/A N/A N/A N/A

pgrowlocks 1.1 1.1 1.1 1.1

plco ee 1.4.4 1.4.4 1.4.4 1.4.4

plls 1.4.4 1.4.4 1.4.4 1.4.4

overview.html)

dev/Topology.html)

fdw.html)

parser.html)

tsm_system_rows N/A N/A 1.0 1.0
rows.html)
tsm_system_time N/A N/A 1.0 1.0

time.html)

Module 9.5.2 9.5.4 9.5.6 9.5.7 9.5.9 9.5.12 9.5.13 9.5

auto_explain N/A N/A N/A Supported Supported Supported Supported Su
test_decoding N/A N/A Supported Supported Supported Supported Supported Su
wal2json N/A N/a N/A Commit Commit Commit Commit Co
hash hash hash hash ha
2828409 2828409 2828409 2828409 28
The following tables show the PostgreSQL extensions and modules for PostgreSQL version
9.4.x that are currently supported by PostgreSQL on Amazon RDS. "N/A" indicates that the
Extension 9.4.7 9.4.9 9.4.11 9.4.1

address_standardizer N/A N/A N/A N/A
address_standardizer_data_us N/A N/A N/A N/A

bloom (https://www.postgresql.org/docs/9.6/static/bloom.html) N/A N/A N/A N/A

gist.html)



hstore_plperl N/A N/A N/A N/A

log_fdw—see Using the log_fdw Extension N/A N/A N/A N/A

pg_bu ercache 1.0 1.0 1.0 1.0
pg_freespacemap N/A N/A N/A N/A

pg_hint_plan (http://pghintplan.osdn.jp/pg_hint_plan.html) N/A N/A N/A N/A

pg_prewarm 1.0 1.0 1.0 1.0


pg_visibility N/A N/A N/A N/A

pgrowlocks 1.1 1.1 1.1 1.1

plco ee 1.4.4 1.4.4 1.4.4 1.4.4

plls 1.4.4 1.4.4 1.4.4 1.4.4
overview.html)

dev/Topology.html)

fdw.html)

parser.html)

tsm_system_rows N/A N/A N/A N/A
rows.html)
tsm_system_time N/A N/A N/A N/A

time.html)

Module 9.4.7 9.4.9 9.4.11 9.4.12 9.4.14 9.4.17

test_decoding N/A N/A N/A Supported Supported Supported
Note
Amazon RDS for PostgreSQL has deprecated PostgreSQL version 9.3.x. We
strongly recommend that you upgrade to a major version, preferably version 9.6.x
or 10.x. See Upgrading the PostgreSQL DB Engine for Amazon RDS
(USER_UpgradeDBInstance.PostgreSQL.html) .
The following table shows PostgreSQL extensions for PostgreSQL version 9.3.x that are
currently supported by PostgreSQL on Amazon RDS. "N/A" indicates that the extension is not
available for that PostgreSQL version. For more information on PostgreSQL extensions, see
Packaging Related Objects into an Extension (https://www.postgresql.org/docs/9.6/static/extend-
extensions.html) .
Extension 9.3.12 9.3.14 9.3.16 9.3

address_standardizer N/A N/A N/A N/
address_standardizer_data_us N/A N/A N/A N/

bloom (https://www.postgresql.org/docs/9.6/static/bloom.html) N/A N/A N/A N/

gist.html)




hstore_plperl N/A N/A N/A N/

ip4r (https://github.com/RhodiumToad/ip4r) N/A N/A N/A N/
log_fdw—see Using the log_fdw Extension N/A N/A N/A N/

pg_bu ercache N/A N/A N/A N/
pg_freespacemap N/A N/A N/A N/

pg_hint_plan (http://pghintplan.osdn.jp/pg_hint_plan.html) N/A N/A N/A N/

pg_prewarm N/A N/A N/A N/


pg_visibility N/A N/A N/A N/

pgrowlocks 1.1 1.1 1.1 1.1
pgstattuple N/A N/A N/A N/

plco ee 1.4.4 1.4.4 1.4.4 1.4

plls 1.4.4 1.4.4 1.4.4 1.4

overview.html)
plv8 (https://github.com/plv8) 1.4.4 1.4.4 1.4.4 1.4

PostGIS (http://www.postgis.net/) 2.1.8 2.1.8 2.1.8 2.1
postgis_tiger_geocoder (http://postgis.net/docs/Geocode.html) 2.1.8 2.1.8 2.1.8 2.1
postgis_topology (http://postgis.net/docs/manual- 2.1.8 2.1.8 2.1.8 2.1
dev/Topology.html)

fdw.html)

parser.html)

tsm_system_rows N/A N/A N/A N/
rows.html)
tsm_system_time N/A N/A N/A N/

time.html)

PostgreSQL Extension Support for PostGIS on Amazon RDS
Before you can use the PostGIS extension, you must create it by running the following
command.
CREATE EXTENSION POSTGIS;
The following table shows the PostGIS component versions that ship with the Amazon RDS
for PostgreSQL versions.
PostgreSQL PostGIS GEOS GDAL PROJ

9.3.12 2.1.8 3.5.0-CAPI-1.9.0 1.11.4, released Rel. 4.9.2, September
r13780 r4084 2016/01/25 8th, 2015

r13780 r4084 2016/07/01 8th, 2015

r13780 r4084 2016/07/01 8th, 2015

r13780 r4084 2016/07/01 8th, 2015

r13780 r4084 2016/01/25 8th, 2015

r13780 r4084 2016/07/01 8th, 2015

r13780 r4084 2016/07/01 8th, 2015

r13780 r4084 2016/07/01 8th, 2015

r14797 r4084 2016/01/26 8th, 2015

r14797 r4084 2016/07/01 8th, 2015

r15298 r4246 2016/07/01 15th, 2016

r15298 r4246 2016/07/01 15th, 2016

r15146 r4084 2016/07/07 8th, 2016

r15302 r4246 2017/20/01 15th, 2016

r15302 r4246 2017/20/01 15th, 2016

r16009 4d2925d6 2017/20/01 15th, 2016

r16009 4d2925d6 2017/20/01 15th, 2016
r16523 4d2925d6 2017/06/23 15th, 2016

r16523 4d2925d6 2017/06/23 15th, 2016

r16523 4d2925d6 2017/06/23 15th, 2016
10.1 2.4.2 3.6.2-CAPI-1.10.2 2.1.3, released Rel. 4.9.3, September

4d2925d6 2017/20/01 15th, 2016
4d2925d6 2017/20/01 15th, 2016
r16526 4d2925d6 2017/06/23 15th, 2016

r16526 4d2925d6 2017/06/23 15th, 2016
r16526 4d2925d6 2017/06/23 15th, 2016
r17027 673b9939 2018/06/22 15th, 2018
Note
PostgreSQL 10.5 added support for the libprotobuf extension version 1.3.0 to
the PostGIS component.
Using the log_fdw Extension
The log_fdw extension is new for Amazon RDS for PostgreSQL version 9.6.2 and later. Using
this extension, you can access your database engine log using a SQL interface. In addition to
viewing the stderr log les that are generated by default on RDS, you can view CSV logs (set
the log_destination parameter to csvlog) and build foreign tables with the data neatly
split into several columns.
This extension introduces two new functions that make it easy to create foreign tables for
database logs:
list_postgres_log_files() – Lists the les in the database log directory and the le
size in bytes.
create_foreign_table_for_log_file(table_name text, server_name text,

log_file_name text) – Builds a foreign table for the speci ed le in the current
database.
All functions created by log_fdw are owned by rds_superuser. Members of the

rds_superuser role can grant access to these functions to other database users.
The following example shows how to use the log_fdw extension.
To use the log_fdw extension
1. Get the log_fdw extension.
postgres=> CREATE EXTENSION log_fdw;

CREATE EXTENSION
2. Create the log server as a foreign data wrapper.
postgres=> CREATE SERVER log_server FOREIGN DATA WRAPPER log_fdw;

CREATE SERVER
3. Select all from a list of log les.
postgres=> SELECT * from list_postgres_log_files() order by 1;
A sample response is as follows.
file_name | file_size_bytes
----------------------------------+-----------------
postgresql.log.2016-08-09-22.csv | 1111
(4 rows)
4. Create a table with a single 'log_entry' column for non-CSV les.

postgres=> SELECT create_foreign_table_for_log_file('my_postgres_error_log',

'log_server', 'postgresql.log.2016-08-09-22.csv');
-----------------------------------
(1 row)
5. Select a sample of the log le. The following code retrieves the log time and error
message description.
postgres=> SELECT log_time, message from my_postgres_error_log order by 1;
log_time | message
----------------------------------+----------------------------------------------
-----------------------------
Tue Aug 09 15:45:18.172 2016 PDT | ending log output to stderr
Tue Aug 09 15:45:18.175 2016 PDT | database system was interrupted; last known up
at 2016-08-09 22:43:34 UTC
Tue Aug 09 15:45:18.223 2016 PDT | checkpoint record is at 0/90002E0
Tue Aug 09 15:45:18.223 2016 PDT | redo record is at 0/90002A8; shutdown FALSE
Tue Aug 09 15:45:18.223 2016 PDT | next transaction ID: 0/1879; next OID: 24578
Tue Aug 09 15:45:18.223 2016 PDT | next MultiXactId: 1; next MultiXactOffset: 0
Tue Aug 09 15:45:18.223 2016 PDT | oldest unfrozen transaction ID: 1822, in
database 1
(7 rows)
Upgrade PL/v8
If you use PL/v8 and upgrade PostgreSQL to a new PL/v8 version, you immediately take
advantage of the new extension but the catalog metadata doesn't re ect this fact. The
following steps synchronize your catalog metadata with the new version of PL/v8. These
steps are optional but we highly recommended you complete them to avoid metadata
mismatch warnings.
1. Verify that you need to update.
Run the following command while connected to your instance.
select * from pg_available_extensions where name in

('plv8','plls','plcoffee');
If your results contain values for an installed version that is a lower number than the
default version, you should continue with this procedure to update your extensions.
For example, the following result set indicates you should update:
name | default_version | installed_version | comment

--------+-----------------+-------------------+----------------------------------
----------------
plls | 2.1.0 | 1.5.3 | PL/LiveScript (v8) trusted
procedural language
plcoffee| 2.1.0 | 1.5.3 | PL/CoffeeScript (v8) trusted
procedural language
plv8 | 2.1.0 | 1.5.3 | PL/JavaScript (v8) trusted
procedural language
(3 rows)
2. Take a snapshot of your instance.
The upgrade drops all your PL/v8 functions. Take a snapshot of your instance as a
precaution. You can continue with the following steps while the snapshot is being
created.
For steps to create a snapshot see, Creating a DB Snapshot (USER_CreateSnapshot.html)
3. Get a count of the functions you need to drop and recreate.
Obtain the count of the number of PL/v8 functions in your instance so you can validate
that they are all in place after the upgrade.
The following code returns the number of functions written in PL/v8, plco ee, or plls:
select proname, nspname, lanname

from pg_proc p, pg_language l, pg_namespace n
where p.prolang = l.oid
and n.oid = p.pronamespace
and lanname in ('plv8','plcoffee','plls');
4. Use pg_dump to create a schema-only dump le.
The following code creates a le on your client machine in the /tmp directory.
./pg_dump -Fc --schema-only -U master postgres > /tmp/test.dmp
This example uses the following ags:
-FC "format custom"

--schema-only "will only dump commands necessary to create schema (functions
in our case)"
-U "rds master username"
database "the database name in our instance"
For more information on pg_dump see, pg_dump

(https://www.postgresql.org/docs/current/static/app-pgdump.html ) .
5. Extract the "CREATE FUNCTION" DDL statement that is present in the dump le.
The following code extracts the DDL statement needed to create the functions. You use
this in subsequent steps to recreate the functions. The code uses the grep command to
extract the statements to a le.
./pg_restore -l /tmp/test.dmp | grep FUNCTION > /tmp/function_list/
For more information on pg_restore see, pg_restore

(https://www.postgresql.org/docs/current/static/app-pgrestore.html) .
6. Drop the functions and extensions.
The following code drops any PL/v8 based objects. The cascade option ensures that any
dependent are dropped.
drop extension plv8 cascade;
If your PostgreSQL instance contains objects based on plco ee or plls, repeat this step
for those extensions.
7. Create the extensions.
The following code creates the PL/v8, plco ee, and plls extensions:
create extension plv8;
create extension plcoffee;
create extension plls;
8. Create the functions using the dump le and "driver" le.
The following code re-creates the functions that you extracted previously.
./pg_restore -U master -d postgres -Fc -L /tmp/function_list

/tmp/test.dmp
9. Verify your functions count.
Validate that your functions have all been re-creating by re-running the following code:
select * from pg_available_extensions where name in

('plv8','plls','plcoffee');
Note
PL/v8 version 2 adds the following extra row to your result set:
proname | nspname | lanname

---------------+------------+----------
plv8_version | pg_catalog | plv8
Supported PostgreSQL Features
Amazon RDS supports many of the most common PostgreSQL features. These include:
Topics
Logical Replication for PostgreSQL on Amazon RDS

(#PostgreSQL.Concepts.General.FeatureSupport.LogicalReplication)
Event Triggers for PostgreSQL on Amazon RDS
(#PostgreSQL.Concepts.General.FeatureSupport.EventTriggers)
Huge Pages for Amazon RDS for PostgreSQL
(#PostgreSQL.Concepts.General.FeatureSupport.HugePages)
Tablespaces for PostgreSQL on Amazon RDS
(#PostgreSQL.Concepts.General.FeatureSupport.Tablespaces)
Autovacuum for PostgreSQL on Amazon RDS
(#PostgreSQL.Concepts.General.FeatureSupport.Autovacuum)
RAM Disk for the stats_temp_directory
(#PostgreSQL.Concepts.General.FeatureSupport.RamDisk)
ALTER ENUM for PostgreSQL (#PostgreSQL.Concepts.General.FeatureSupport.AlterEnum)
Logical Replication for PostgreSQL on Amazon RDS
Beginning with PostgreSQL version 10.4, RDS supports the publication and subscription SQL
Syntax for PostgreSQL 10 Logical Replication.
To enable logical replication for an Amazon RDS for PostgreSQL DB instance
1. The AWS user account requires the rds_superuser role to perform logical replication for
the PostgreSQL database on Amazon RDS.
2. Set the rds.logical_replication static parameter to 1.
3. Modify the inbound rules of the security group for the publisher instance (production)
to allow the subscriber instance (replica) to connect. This is usually done by including
the IP address of the subscriber in the security group.
4. Restart the DB instance for the changes to the static parameter

rds.logical_replication to take e ect.
For more information on PostgreSQL logical replication, see the PostgreSQL documentation
(https://www.postgresql.org/docs/10/static/logical-replication.html) .
Logical Decoding and Logical Replication
Beginning with PostgreSQL version 9.4, RDS supports the streaming of WAL changes using
logical replication slots. Amazon RDS supports logical decoding for a PostgreSQL DB instance
version 9.4.9 and higher and 9.5.4 and higher. You can set up logical replication slots on your
instance and stream database changes through these slots to a client such as
pg_recvlogical. Logical replication slots are created at the database level and support
replication connections to a single database.
The most common clients for PostgreSQL logical replication are the AWS Database Migration
Service or a custom-managed host on an AWS EC2 instance. The logical replication slot knows
nothing about the receiver of the stream, and there is no requirement that the target be a
replica database. If you set up a logical replication slot and don't read from the slot, data can
be written and quickly ll up your DB instance's storage.
PostgreSQL logical replication and logical decoding on Amazon RDS are enabled with a
parameter, a replication connection type, and a security role. The client for logical decoding
can be any client that is capable of establishing a replication connection to a database on a
PostgreSQL DB instance.
To enable logical decoding for an Amazon RDS for PostgreSQL DB instance
1. The user account requires the rds_superuser role to enable logical replication. The user
account also requires the rds_replication role to grant permissions to manage logical
slots and to stream data using logical slots.
2. Set the rds.logical_replication static parameter to 1. As part of applying this

parameter, we also set the parameters wal_level, max_wal_senders,
max_replication_slots, and max_connections. These parameter changes can
increase WAL generation, so you should only set the rds.logical_replication
parameter when you are using logical slots.
3. Reboot the DB instance for the static rds.logical_replication parameter to take

e ect.
4. Create a logical replication slot as explained in the next section. This process requires
that you specify a decoding plugin. Currently we support the test_decoding output
plugin that ships with PostgreSQL.
For more information on PostgreSQL logical decoding, see the PostgreSQL documentation
(https://www.postgresql.org/docs/current/static/logicaldecoding-explanation.html) .
Working with Logical Replication Slots
You can use SQL commands to work with logical slots. For example, the following command
creates a logical slot named test_slot using the default PostgreSQL output plugin
test_decoding.
SELECT * FROM pg_create_logical_replication_slot('test_slot', 'test_decoding');
The output should be similar to the following.
slot_name | xlog_position
-----------------+---------------
regression_slot | 0/16B1970
(1 row)
To list logical slots, use the following command.
SELECT * FROM pg_replication_slots;
To drop a logical slot, use the following command.
SELECT pg_drop_replication_slot('test_slot');
The output should be similar to the following.
pg_drop_replication_slot
-----------------------
(1 row)
For more examples on working with logical replication slots, see Logical Decoding Examples
(https://www.postgresql.org/docs/9.5/static/logicaldecoding-example.html) in the PostgreSQL
documentation.
Once you create the logical replication slot, you can start streaming. The following example
shows how logical decoding is controlled over the streaming replication protocol, using the
program pg_recvlogical included in the PostgreSQL distribution. This requires that client
authentication is set up to allow replication connections.
pg_recvlogical -d postgres --slot test_slot -U master

--host sg-postgresql1.c6c8mresaghgv0.us-west-2.rds.amazonaws.com
-f - --start
Event Triggers for PostgreSQL on Amazon RDS
level, so they can apply to all databases on an instance.
For example, the following code creates an event trigger that prints the current user at the
end of every DDL command.
CREATE OR REPLACE FUNCTION raise_notice_func()

RETURNS event_trigger
LANGUAGE plpgsql AS
$$
BEGIN
RAISE NOTICE 'In trigger function: %', current_user;
END;
$$;
CREATE EVENT TRIGGER event_trigger_1

ON ddl_command_end
EXECUTE PROCEDURE raise_notice_func();
For more information about PostgreSQL event triggers, see Event Triggers
(https://www.postgresql.org/docs/current/static/event-triggers.html) in the PostgreSQL
documentation.
There are several limitations to using PostgreSQL event triggers on Amazon RDS. These
include:
You cannot create event triggers on read replicas. You can, however, create event
triggers on a read replica master. The event triggers are then copied to the read replica.
The event triggers on the read replica don't re on the read replica when changes are
pushed from the master. However, if the read replica is promoted, the existing event
triggers re when database operations occur.
To perform a major version upgrade to a PostgreSQL DB instance that uses event
triggers, you must delete the event triggers before you upgrade the instance.
Huge Pages for Amazon RDS for PostgreSQL
Amazon RDS for PostgreSQL supports multiple page sizes for PostgreSQL versions 9.4.11 and
later, 9.5.6 and later, and 9.6.2 and later. This support includes 4 K and 2 MB page sizes.
Huge pages reduce overhead when using large contiguous chunks of memory. You allocate
huge pages for your application by using calls to mmap or SYSV shared memory. You enable
huge pages on an Amazon RDS for PostgreSQL database by using the huge_pages parameter.
Set this parameter to "on" to enable huge pages.
For PostgreSQL versions 10 and above, huge pages are enabled for all instance classes. For
PostgreSQL versions below 10, huge pages are enabled by default for db.r4.*,
db.m4.16xlarge, and db.m5.* instance classes. For other instance classes, huge pages are
disabled by default.
When you set the huge_pages parameter to "on," Amazon RDS uses huge pages based on the
available shared memory. If the DB instance is unable to use huge pages due to shared
memory constraints, Amazon RDS prevents the instance from starting and sets the status of
the DB instance to an incompatible parameters state. In this case, you can set the huge_pages
parameter to "o " to allow Amazon RDS to start the DB instance.
The shared_buffers parameter is key to setting the shared memory pool that is required for
using huge pages. The default value for the shared_buffers parameter is set to a percentage
of the total 8K pages available for that instance's memory. When you use huge pages, those
pages are allocated in the huge pages collocated together. Amazon RDS puts a DB instance
into an incompatible parameters state if the shared memory parameters are set to require
more than 90 percent of the DB instance memory. For more information about setting shared
memory for PostgreSQL, see the PostgreSQL documentation
(https://www.postgresql.org/docs/9.6/static/runtime-con g-resource.html) .
Note
Huge pages are not supported for the db.m1, db.m2, and db.m3 DB instance
classes.
Tablespaces for PostgreSQL on Amazon RDS
Tablespaces are supported in PostgreSQL on Amazon RDS for compatibility; since all storage
is on a single logical volume, tablespaces cannot be used for IO splitting or isolation. We have
benchmarks and practical experience that shows that a single logical volume is the best setup
for most use cases.
Autovacuum for PostgreSQL on Amazon RDS
The PostgreSQL autovacuum feature is turned on by default for new PostgreSQL DB

instances. Autovacuum is optional, but we highly recommend that you do not turn
autovacuum o . For more information on using autovacuum with Amazon RDS for
PostgreSQL, see Working with PostgreSQL Autovacuum on Amazon RDS
(Appendix.PostgreSQL.CommonDBATasks.html#Appendix.PostgreSQL.CommonDBATasks.Autovacuum)
.
RAM Disk for the stats_temp_directory
The Amazon RDS for PostgreSQL parameter, rds.pg_stat_ramdisk_size, can be used to

specify the system memory allocated to a RAM disk for storing the PostgreSQL
stats_temp_directory. The RAM disk parameter is available for all PostgreSQL versions on
Amazon RDS.
Under certain workloads, setting this parameter can improve performance and decrease IO
requirements. For more information about the stats_temp_directory, see the PostgreSQL
documentation. (https://www.postgresql.org/docs/current/static/runtime-con g-statistics.html#GUC-
STATS-TEMP-DIRECTORY)
To enable a RAM disk for your stats_temp_directory, set the rds.pg_stat_ramdisk_size

parameter to a non-zero value in the parameter group used by your DB instance. The
parameter value is in MB. You must reboot the DB instance before the change takes e ect.
For example, the following AWS CLI command sets the RAM disk parameter to 256 MB.
postgres=>aws rds modify-db-parameter-group \

--db-parameter-group-name pg-95-ramdisk-testing \
--parameters "ParameterName=rds.pg_stat_ramdisk_size, ParameterValue=256,
ApplyMethod=pending-reboot"
After you reboot, run the following command to see the status of the
stats_temp_directory:
postgres=>show stats_temp_directory;
The command should return the following:
stats_temp_directory
---------------------------
/rdsdbramdisk/pg_stat_tmp
(1 row)
ALTER ENUM for PostgreSQL
Amazon RDS for PostgreSQL versions 9.6.2 and 9.5.6 and later support the ability to alter
enumerations. This feature is not available in other versions on Amazon RDS.
The following code shows an example of altering an enum value.
postgres=> CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue',
'purple');
CREATE TYPE
postgres=> CREATE TABLE t1 (colors rainbow);
CREATE TABLE
postgres=> INSERT INTO t1 VALUES ('red'), ( 'orange');
INSERT 0 2
postgres=> SELECT * from t1;
colors
--------
red
orange
(2 rows)
postgres=> ALTER TYPE rainbow RENAME VALUE 'red' TO 'crimson';
ALTER TYPE
postgres=> SELECT * from t1;
colors
---------
crimson
orange
(2 rows)
Limits for PostgreSQL DB Instances
The following is a list of limitations for PostgreSQL on Amazon RDS:
You can have up to 40 PostgreSQL DB instances.

For storage limits, see Amazon RDS DB Instance Storage (CHAP_Storage.html) .
Amazon RDS reserves up to 3 connections for system maintenance. If you specify a
value for the user connections parameter, you need to add 3 to the number of
connections that you expect to use.
There are two types of upgrades you can manage for your PostgreSQL DB instance:
OS Updates – Occasionally, Amazon RDS might need to update the underlying

operating system of your DB instance to apply security xes or OS changes. You can
decide when Amazon RDS applies OS updates by using the RDS console, AWS Command
Line Interface (AWS CLI), or RDS API.
For more information about OS updates, see Applying Updates for a DB Instance
(USER_UpgradeDBInstance.Maintenance.html#USER_UpgradeDBInstance.OSUpgrades) .
Database Engine Upgrades – When Amazon RDS supports a new version of a database
engine, you can upgrade your DB instances to the new version. There are two kinds of
upgrades: major version upgrades and minor version upgrades. Amazon RDS supports
both major and minor version upgrades for PostgreSQL DB instances.
For more information about PostgreSQL DB engine upgrades, see Upgrading the
PostgreSQL DB Engine for Amazon RDS (USER_UpgradeDBInstance.PostgreSQL.html) .
Using SSL with a PostgreSQL DB Instance
Amazon RDS supports Secure Socket Layer (SSL) encryption for PostgreSQL DB instances.
Using SSL, you can encrypt a PostgreSQL connection between your applications and your
PostgreSQL DB instances. You can also force all connections to your PostgreSQL DB instance
to use SSL.
Topics
Requiring an SSL Connection to a PostgreSQL DB Instance

(#PostgreSQL.Concepts.General.SSL.Requiring)
Determining the SSL Connection Status (#PostgreSQL.Concepts.General.SSL.Status)
SSL support is available in all AWS regions for PostgreSQL. Amazon RDS creates an SSL
certi cate for your PostgreSQL DB instance when the instance is created. If you enable SSL
certi cate veri cation, then the SSL certi cate includes the DB instance endpoint as the
Common Name (CN) for the SSL certi cate to guard against spoo ng attacks.
To connect to a PostgreSQL DB instance over SSL
1. Download the certi cate stored at https://s3.amazonaws.com/rds-downloads/rds-

combined-ca-bundle.pem (https://s3.amazonaws.com/rds-downloads/rds-combined-ca-
bundle.pem) .
2. Import the certi cate into your operating system.
3. Connect to your PostgreSQL DB instance over SSL by appending sslmode=verify-full

to your connection string. When you use sslmode=verify-full, the SSL connection
veri es the DB instance endpoint against the endpoint in the SSL certi cate.
Use the sslrootcert parameter to reference the certi cate, for example,
sslrootcert=rds-ssl-ca-cert.pem.
The following is an example of using the psql program to connect to a PostgreSQL DB

instance :
$ psql -h testpg.cdhmuqifdpib.us-east-1.rds.amazonaws.com -p 5432 \

"dbname=testpg user=testuser sslrootcert=rds-ca-2015-root.pem sslmode=verify-full"
Requiring an SSL Connection to a PostgreSQL DB Instance
You can require that connections to your PostgreSQL DB instance use SSL by using the
rds.force_ssl parameter. By default, the rds.force_ssl parameter is set to 0 (o ). You
can set the rds.force_ssl parameter to 1 (on) to require SSL for connections to your DB
instance. Updating the rds.force_ssl parameter also sets the PostgreSQL ssl parameter to
1 (on) and modi es your DB instance’s pg_hba.conf le to support the new SSL
con guration.
You can set the rds.force_ssl parameter value by updating the parameter group for your
DB instance. If the parameter group for your DB instance isn't the default one, and the ssl
parameter is already set to 1 when you set rds.force_ssl to 1, you don't need to reboot
your DB instance. Otherwise, you must reboot your DB instance for the change to take e ect.
For more information on parameter groups, see Working with DB Parameter Groups
(USER_WorkingWithParamGroups.html) .
When the rds.force_ssl parameter is set to 1 for a DB instance, you see output similar to
the following when you connect, indicating that SSL is now required:
$ psql postgres -h SOMEHOST.amazonaws.com -p 8192 -U someuser

psql (9.3.12, server 9.4.4)
WARNING: psql major version 9.3, server major version 9.4.
Some psql features might not work.
SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
Type "help" for help.
postgres=>
Determining the SSL Connection Status
The encrypted status of your connection is shown in the logon banner when you connect to
the DB instance:
Password for user master:

psql (9.3.12)
SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
Type "help" for help.
postgres=>
You can also load the sslinfo extension and then call the ssl_is_used() function to
determine if SSL is being used. The function returns t if the connection is using SSL,
otherwise it returns f.
postgres=> create extension sslinfo;

CREATE EXTENSION
postgres=> select ssl_is_used();

ssl_is_used
---------
t
(1 row)
You can use the select ssl_cipher() command to determine the SSL cipher:
postgres=> select ssl_cipher();

ssl_cipher
--------------------
DHE-RSA-AES256-SHA
(1 row)
If you enable set rds.force_ssl and restart your instance, non-SSL connections are refused
with the following message:
$ export PGSSLMODE=disable
$ psql postgres -h SOMEHOST.amazonaws.com -p 8192 -U someuser
psql: FATAL: no pg_hba.conf entry for host "host.ip", user "someuser", database
"postgres", SSL off
$
© 2019, Amazon Web Services, Inc. or its a liates. All rights reserved.

PostgreSQL On Amazon RDS - Amazon Relational Database Service PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PostgreSQL On Amazon RDS - Amazon Relational Database Service PDF

Uploaded by

Copyright:

Available Formats

10/1/2019 PostgreSQL on Amazon RDS - Amazon Relational Database Service

The AWS Documentation website is getting a new look!

Common Management Tasks for PostgreSQL on Amazon RDS

Common Management Tasks for PostgreSQL on Amazon RDS

Setting up Amazon RDS for rst-time use

Understanding Amazon RDS DB instances

Finding supported PostgreSQL versions

Amazon RDS supports several versions of PostgreSQL.

Setting up high availability and failover support

A production DB instance should use Multi-AZ deployments. Multi-AZ deployments provide

Understanding the Amazon Virtual Private Cloud (VPC) network

Importing data into Amazon RDS PostgreSQL

Setting up read-only Read Replicas (masters and standbys)

Understanding security groups

Setting up parameter groups and features

Performing common DBA tasks for PostgreSQL

Some of the more common tasks for PostgreSQL DBAs include:

Working with PostgreSQL Parameters

Connecting to your PostgreSQL DB instance

Backing up and restoring your DB instance

Monitoring the activity and performance of your DB instance

Upgrading the PostgreSQL database version

Working with log les

Understanding the best practices for PostgreSQL DB instances

Working with the Database Preview Environment

DB instances in the Database Preview Environment are similar to DB instances in a production

Features Not Supported in the Preview Environment (#preview-environment-exclusions)

Features Not Supported in the Preview Environment

The following features are not available in the preview environment:

Cross-region snapshot copy

PostgreSQL Extensions Supported in the Preview Environment

pg_bu ercache 1.3

Creating a New DB Instance in the Preview Environment

Use the following procedure to create a DB instance in the preview environment.

To create a DB instance in the preview environment

2. Choose Dashboard from the navigation pane.

3. Choose Switch to database preview environment.

If you want to create an instance in the Database Preview Environment with

4. Continue with the procedure as described in New Console

Amazon RDS for PostgreSQL Versions and Extensions

Supported PostgreSQL Database Versions (#PostgreSQL.Concepts.General.DBVersions)

Supported PostgreSQL Database Versions

Amazon RDS supports the following PostgreSQL versions.

PostgreSQL Version 12 Beta 3 on Amazon RDS in the Database Preview Environment

PostgreSQL Version 9.6.1 on Amazon RDS (#PostgreSQL.Concepts.General.version961)

PostgreSQL Version 12 Beta 3 on Amazon RDS in the Database Preview Environment

PostgreSQL version 12 Beta 3 contains several improvements that are described in

PostgreSQL Version 12 Beta 2 on Amazon RDS in the Database Preview Environment

PostgreSQL 12 Beta 1 Released! (https://www.postgresql.org/about/news/1943/)

PostgreSQL Version 11.4 on Amazon RDS

PostgreSQL Version 11.2 on Amazon RDS

This version also includes the following changes:

A new pgTAP (https://pgtap.org/) extension version 1.0.

PostgreSQL Version 11.1 on Amazon RDS

Partitioning – Partitioning improvements include support for hash partitioning,

PostgreSQL Version 11 on Amazon RDS in the Database Preview Environment

PostgreSQL Version 11 on Amazon RDS has been released in the production

PostgreSQL version 11 contains several improvements that are described in PostgreSQL 11

PostgreSQL Version 10.9 on Amazon RDS

PostgreSQL Version 10.7 on Amazon RDS

This version also includes the following changes:

PostgreSQL Version 10.6 on Amazon RDS