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 12

  1. You have to keep in mind that the user always knows more than the database engine itself. In addition to that, the administrator has access to a lot of external information about the operating system, hardware, user patterns, and all that. A database engine cannot decide whether a user's query is pointless or not—it does not know its purpose. Therefore, administrators and developers are always at an advantage over the database and are, therefore, necessary (and most likely always will be). 
  2. No. My company provides services for thousands of businesses. We rarely see cases of database corruption—and if there is corruption, it is usually caused by hardware issues.
  3. Usually not, unless you are using the database in a suboptimal way. In general, PostgreSQL does a lot of stuff on its own and takes care of many things, such as VACUUM, automatically...