Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
PostgreSQL 13 Cookbook

You're reading from   PostgreSQL 13 Cookbook Over 120 recipes to build high-performance and fault-tolerant PostgreSQL database solutions

Arrow left icon
Product type Paperback
Published in Feb 2021
Publisher Packt
ISBN-13 9781838648138
Length 344 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Author (1):
Arrow left icon
Vallarapu Naga Avinash Kumar Vallarapu Naga Avinash Kumar
Author Profile Icon Vallarapu Naga Avinash Kumar
Vallarapu Naga Avinash Kumar
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Cluster Management Fundamentals 2. Cluster Management Techniques FREE CHAPTER 3. Backup and Recovery 4. Advanced Replication Techniques 5. High Availability and Automatic Failover 6. Connection Pooling and Load Balancing 7. Securing through Authentication 8. Logging and Analyzing PostgreSQL Servers 9. Critical Services Monitoring 10. Extensions and Performance Tuning 11. Upgrades and Patches 12. About Packt 13. Other Books You May Enjoy

Major version upgrade to PostgreSQL 13 using pg_upgrade with downtime

In order to simplify the database upgrades, there is a utility that is built into the community PostgreSQL software: pg_upgrade. We can avoid performing a globals dump or database dump and directly run the upgrade using a single command when using pg_upgrade. In this recipe, we shall see how this utility can be used to perform simple database upgrades.

Getting ready

In order to perform an upgrade using pg_upgrade, we need to have sufficient space in the server. If the upgrade is being performed within the same server, then we need to make sure that we have at least three times the space of the existing database cluster (excluding the space required by WAL segments and log files).

As an example, if we have a PostgreSQL 9.3 cluster of size 100 GB, we should have the following:

  • 100 GB dedicated to the new PostgreSQL 13 cluster.
  • An additional 100 GB for storing the backup dump generated using pg_dumpall.
  • While performing...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image