Thread: Partitioning tables

Assume you are reading and writing regularly to a given table. 

1) When using Amazon RDS PostgreSQL 10, is there any reason to use table partitioning? 

2) If so what might be a few simple examples of when to use it? 

3) Also, if there is a reason then how large should a table be before it should be partitioned?  I am just wanting some general idea or scope. 

It is always a good idea to occasionally revaluate if going down a particular path still makes sense.

Thanks,

Lance

Assume you are reading and writing regularly to a given table. 

1) When using Amazon RDS PostgreSQL 10, is there any reason to use table partitioning? 

2) If so what might be a few simple examples of when to use it? 

3) Also, if there is a reason then how large should a table be before it should be partitioned?  I am just wanting some general idea or scope. 

It is always a good idea to occasionally revaluate if going down a particular path still makes sense.

Thanks,

Lance

RDS for PostgreSQL 10, and prior versions of RDS for PostgreSQL, run on EBS storage. One key benefit of table partitioning is partition elimination for queries that would otherwise scan the entire table, and this benefit applies to RDS for PostgreSQL. More generally, the benefits described in the postgresql.org doc here - https://www.postgresql.org/docs/10/static/ddl-partitioning.html - are applicable for RDS for PostgreSQL, except for the last one listed – Seldom-used data can be migrated to cheaper and slower storage media.

Kevin Jernigan

Senior Product Manager

Amazon Aurora PostgreSQL

1-415-710-8828 (m)

kmj@amazon.com

27 Melcher Street

Boston, MA  02210