Book Image

PostgreSQL 16 Administration Cookbook

By : Gianni Ciolli, Boriss Mejías, Jimmy Angelakos, Vibhor Kumar, Simon Riggs
5 (1)
Book Image

PostgreSQL 16 Administration Cookbook

5 (1)
By: Gianni Ciolli, Boriss Mejías, Jimmy Angelakos, Vibhor Kumar, Simon Riggs

Overview of this book

PostgreSQL has seen a huge increase in its customer base in the past few years and is becoming one of the go-to solutions for anyone who has a database-specific challenge. This PostgreSQL book touches on all the fundamentals of Database Administration in a problem-solution format. It is intended to be the perfect desk reference guide. This new edition focuses on recipes based on the new PostgreSQL 16 release. The additions include handling complex batch loading scenarios with the SQL MERGE statement, security improvements, running Postgres on Kubernetes or with TPA and Ansible, and more. This edition also focuses on certain performance gains, such as query optimization, and the acceleration of specific operations, such as sort. It will help you understand roles, ensuring high availability, concurrency, and replication. It also draws your attention to aspects like validating backups, recovery, monitoring, and scaling aspects. This book will act as a one-stop solution to all your real-world database administration challenges. By the end of this book, you will be able to manage, monitor, and replicate your PostgreSQL 16 database for efficient administration and maintenance with the best practices from experts.
Table of Contents (15 chapters)
13
Other Books You May Enjoy
14
Index

Finding good candidates for partition keys

What is a good partition key? The answer is probably close to one that enables you to have the right number of partitions for ease of use and maintainability, but also one that enables partition pruning for your queries for optimal performance.

Getting ready

In order to choose a good partition key for your tables, you need to understand the nature of your data. This means you need to analyze your queries to determine the main keys that you’re using for data retrieval from those tables. Two desirable characteristics of partition keys are:

  • They need to have a high enough cardinality, or range of values, for the number of partitions desired.
  • They need to be columns that don’t change often, in order to avoid having to move rows among partitions.

How to do it…

First off, determine your access patterns for the table in question. See which keys you are selecting data by (the ones that are...