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 8

  1. There are two levels to configure network access. In postgresql.conf (listen_addresses), you can configure the bind addresses, and open remote connections. In pg_hba.conf, you can tell PostgreSQL how to authenticate network connections. Depending on the IP range that a request comes from, different rules can be applied. 
  2. Basically, the difference between a user and a role is academic. When creating a role, the default value is NOLOGIN, which is not the case when you use CREATE USER. Otherwise, roles and users can be considered to be the same. 
  1. This is simple. You can use ALTER USER to do the job, as shown in the following example:
test=# ALTER USER hs PASSWORD 'abc';
ALTER ROLE

Keep in mind that passwords are not necessarily stored in PostgreSQL. If you are using LDAP authentication, or some other external method,...