Book Image

Mastering PostgreSQL 11 - Second Edition

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

Mastering PostgreSQL 11 - Second Edition

By: Hans-Jürgen Schönig

Overview of this book

This second edition of Mastering PostgreSQL 11 helps you build dynamic database solutions for enterprise applications using the latest release of PostgreSQL, which enables database analysts to design both the physical and technical aspects of the system architecture with ease. This book begins with an introduction to the newly released features in PostgreSQL 11 to help you build efficient and fault-tolerant PostgreSQL applications. You’ll examine all of the advanced aspects of PostgreSQL in detail, including logical replication, database clusters, performance tuning, monitoring, and user management. You will also work with the PostgreSQL optimizer, configuring PostgreSQL for high speed, and see how to move from Oracle to PostgreSQL. As you progress through the chapters, you will cover transactions, locking, indexes, and optimizing queries to improve performance. Additionally, you’ll learn to manage network security and explore backups and replications, while understanding the useful extensions of PostgreSQL so that you can optimize the speed and performance of large databases. By the end of this book, you will be able to use your database to its utmost capacity by implementing advanced administrative tasks with ease.
Table of Contents (15 chapters)
Free Chapter
1
PostgreSQL Overview

Q&A

As in most chapters, we will take a look at some key questions arising from what has just been covered:

What kind of runtime statistics does PostgreSQL gather?

There is a lot of information that has been collected by the stats collector in PostgreSQL. A full overview of what there is can be found in the official PostgreSQL documentation, which is available online at https://www.postgresql.org/docs/11/static/monitoring-stats.html.

How can I spot performance problems easily?

There are various ways to detect performance problems in PostgreSQL. One way is to make use of pg_stat_statements. Other options are to use auto_explain or simply standard PostgreSQL log files. Depending on your needs, you can decide on which method is best for you. The following blog shows you how this kind of information can be extracted from the system: https://www.cybertec-postgresql.com/en/3-ways...