Book Image

Mastering PostgreSQL 12 - Third Edition

By : Hans-Jürgen Schönig
Book Image

Mastering PostgreSQL 12 - Third Edition

By: Hans-Jürgen Schönig

Overview of this book

Thanks to its reliability, robustness, and high performance, PostgreSQL has become the most advanced open source database on the market. This third edition of Mastering PostgreSQL helps you build dynamic database solutions for enterprise applications using the latest release of PostgreSQL, which enables database analysts to design both physical and technical aspects of system architecture with ease. Starting with an introduction to the newly released features in PostgreSQL 12, this book will help you build efficient and fault-tolerant PostgreSQL applications. You’ll thoroughly examine the advanced features of PostgreSQL, including logical replication, database clusters, performance tuning, monitoring, and user management. You’ll also work with the PostgreSQL optimizer, configure PostgreSQL for high speed, and understand how to move from Oracle to PostgreSQL. As you progress through the chapters, you’ll cover transactions, locking, indexes, and how to optimize queries for improved performance. Additionally, you’ll learn how to manage network security and explore backups and replications while understanding useful PostgreSQL extensions to help you in optimizing the performance of large databases. By the end of this PostgreSQL book, you’ll be able to get the most out of your database by implementing advanced administrative tasks effortlessly.
Table of Contents (18 chapters)
Free Chapter
1
Section 1: Basic Overview
4
Section 2: Advanced Concepts

Chapter 9

  1. If your database is fairly small, a dump certainly makes sense. However, if your database is huge (> XXX GB), a dump might not be feasible anymore and different means can make sense such as WAL archiving. You also have to keep in mind that a dump only provides a snapshot of data—it does not provide you with point-in-time recovery. Therefore, the dump is more of an additional tool and not a replacement for WAL archiving.
  2. A compressed dump is usually around 10 times faster than the PostgreSQL database that you have saved. The reason is that the database has to store the content of an index while the backup only contains definitions. This makes a huge difference in terms of space consumption. On top of that, PostgreSQL has to store additional metadata such as tuple headers and so on, which also needs space.
  3. Yes, it is definitely necessary to do that.
  4. Yes. If...