Book Image

Learning PostgreSQL 11 - Third Edition

By : Salahaldin Juba, Andrey Volkov
Book Image

Learning PostgreSQL 11 - Third Edition

By: Salahaldin Juba, Andrey Volkov

Overview of this book

PostgreSQL is one of the most popular open source database management systems in the world, and it supports advanced features included in SQL standards. This book will familiarize you with the latest features in PostgreSQL 11, and get you up and running with building efficient PostgreSQL database solutions from scratch. Learning PostgreSQL, 11 begins by covering the concepts of relational databases and their core principles. You’ll explore the Data Definition Language (DDL) and commonly used DDL commands supported by ANSI SQL. You’ll also learn how to create tables, define integrity constraints, build indexes, and set up views and other schema objects. As you advance, you’ll come to understand Data Manipulation Language (DML) and server-side programming capabilities using PL/pgSQL, giving you a robust background to develop, tune, test, and troubleshoot your database application. The book will guide you in exploring NoSQL capabilities and connecting to your database to manipulate data objects. You’ll get to grips with using data warehousing in analytical solutions and reports, and scaling the database for high availability and performance. By the end of this book, you’ll have gained a thorough understanding of PostgreSQL 11 and developed the necessary skills to build efficient database solutions.
Table of Contents (18 chapters)

Questions

  1. How can you display the queries that are generated by the psql client to the PostgreSQL server?
  2. What is the purpose of the pg_class table? What is the difference between pg_catalog and information_schema?
  3. What does the abbreviation TOAST stand for and what is it used for?
  4. You work as an administrator and you would like to clean up unused indexes, What are the criteria you can use to find these indexes? Why is it important to monitor usage indexes?
  5. Assume that you have a table with duplicate data due to the lack of unique and primary key constraints. Which column can be used to distinguish the rows?
  6. Can a table have duplicate data even if it has a primary key?
  7. What is the difference between the pg_cancel_backend and pg_terminate_backend functions?
  8. Which is easier to find: unused tables or unused views? And why?
  9. List the contype constraint types found in the pg_constraint...