Book Image

PostgreSQL 11 Administration Cookbook

By : Simon Riggs, Gianni Ciolli, Sudheer Kumar Meesala
Book Image

PostgreSQL 11 Administration Cookbook

By: Simon Riggs, Gianni Ciolli, Sudheer Kumar Meesala

Overview of this book

PostgreSQL is a powerful, open source database management system with an enviable reputation for high performance and stability. With many new features in its arsenal, PostgreSQL 11 allows you to scale up your PostgreSQL infrastructure. This book takes a step-by-step, recipe-based approach to effective PostgreSQL administration. The book will introduce you to new features such as logical replication, native table partitioning, additional query parallelism, and much more to help you to understand and control, crash recovery and plan backups. You will learn how to tackle a variety of problems and pain points for any database administrator such as creating tables, managing views, improving performance, and securing your database. As you make steady progress, the book will draw attention to important topics such as monitoring roles, backup, and recovery of your PostgreSQL 11 database to help you understand roles and produce a summary of log files, ensuring high availability, concurrency, and replication. By the end of this book, you will have the necessary knowledge to manage your PostgreSQL 11 database efficiently.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Preventing new connections


In certain emergencies, you may need to lock down the server completely, or just prevent specific users from accessing the database. It's hard to foresee all the situations in which you might need to do this, so we will present a range of options.

How to do it…

Connections can be prevented in a number of ways, as follows:

  • Pause and resume the session pool. See the Setting up a connection pool recipe later in this chapter on controlling connection pools.
  • Stop the server! See the Stopping the server safely and quickly and the Stopping the server in an emergency recipes, but this is not recommended.
  • Restrict the connections for a specific database to zero, by setting the connection limit to zero:
ALTER DATABASE foo_db CONNECTION LIMIT 0;
  • This will limit normal users from connecting to that database, though it will still allow superuser connections.
  • Restrict the connections for a specific user to zero by setting the connection limit to zero (see the Restricting users to only...