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)

Online analytical processing

A company that runs such a car portal website could store the HTTP access log in a database table. This can be used to analyze user activity; for example, to measure the performance of the application, to identify the patterns in the users' behavior, or simply to collect statistics about which car models are most popular. This data would be inserted into the table and never changed, and maybe deleted only when it is too old. However, the amount of data would be much bigger than the actual business data in the car portal database, but the data would be accessed only from time to time by internal users to perform analysis and create reports.

These users are not expected to execute many queries per second—the opposite in fact, but those queries will be big and complex, therefore the time that each query can take matters.

Another thing about...