Postgres Partitioning Best Practices
Thursday, May 29
11:05 - 11:35
In this session, we’ll look at when and why you might partition your database tables, and answer some of the common questions people have about table partitioning.
You should come away with an understanding of whether partitioning is right for you and how you could go about putting it in place.
As you grapple with ever-growing database systems, you may start to think about table partitioning to help with managing large tables. Many of the customers I work with have gone through that thought process and they often ask questions such as:
- When should I consider partitioning tables in Postgres?
- What are the advantages?
- What are the main considerations?
- Are there any potential pitfalls and, if so, how can they be avoided?
- What are the best practices?
- Which column(s) should I partition on?
- Is Postgres native partitioning enough, or do I need to use other tools as well?
- What kind of application changes will I need to make?
- How can I partition existing tables with minimum downtime?
In this session, we’ll look at when and why partitioning your Postgres tables can be useful, before going on to answer some of those questions.
You should come away with an understanding of whether partitioning is right for you and, if so, how you need to go about putting it in place.
Karen Jex
Karen was a database administrator for over 20 years and was once described as “quite personable for a DBA”, which she decided to take as a compliment! She’s now a Senior Solutions Architect at Crunchy Data, helping her customers to design and manage their (PostgreSQL) database environments.
Karen gives talks about databases at PostgreSQL and developer conferences because she loves sharing knowledge. She is a PostgreSQL Europe board member and conference organiser, and chairs the PostgreSQL Europe Diversity Committee.