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

Adding/removing tablespaces

Tablespaces are a feature in PostgreSQL that allow the user to specify different physical devices on which to store data. We may want to do that for performance or administrative ease, or our database may have run out of disk space.

Getting ready

The very first action, when creating a tablespace in PostgreSQL, is to double-check that you actually need to create a tablespace. This is because tablespaces in PostgreSQL have a different purpose than tablespaces in some other database systems.

The only purpose of having multiple tablespaces is to use a certain directory when storing data files for specific tables or indexes. There are no other implications in terms of crashes or disaster recovery: you need all the tablespaces for the database to operate correctly!

If you are thinking of placing some tables on a separate tablespace so they can be recovered separately from the rest of the database, then know this is not how PostgreSQL works. Relational...