Book Image

PostgreSQL 9.6 High Performance

By : Ibrar Ahmed, Gregory Smith
Book Image

PostgreSQL 9.6 High Performance

By: Ibrar Ahmed, Gregory Smith

Overview of this book

<p>Database administrators and developers spend years learning techniques to configure their PostgreSQL database servers for optimal performance, mostly when they encounter performance issues. Scalability and high availability of the database solution is equally important these days. This book will show you how to configure new database installations and optimize existing database server installations using PostgreSQL 9.6.</p> <p>You will start with the basic concepts of database performance, because all successful database applications are destined to eventually run into issues when scaling up their performance. You will not only learn to optimize your database and queries for optimal performance, but also detect the real performance bottlenecks using PostgreSQL tools and some external tools. Next, you will learn how to benchmark your hardware and tune your operating system. Optimize your queries against the database with the help of right indexes, and monitor every layer, ranging from hardware to queries. Moving on, you will see how connection pooling, caching, partitioning, and replication will help you handle increasing database workloads.</p> <p>Achieving high database performance is not easy, but you can learn it by using the right guide—PostgreSQL 9.6 High Performance.</p>
Table of Contents (25 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Performance features in version 8.2


PostgreSQL version 8.2 introduced some performance features, such as query level performance and sorting performance and improvement in vacuuming. This section describes only the performance features. For a full list of features introduced in version 8.2 look at the release notes of PostgreSQL: https://www.postgresql.org/docs/8.2/static/release-8-2.html

Let's look at the features:

  • Memory settings in the postgresql.conf file can be specified in standard units such as 1 MB, rather than as simply raw integers whose settings depends on the server units.
  • Indexes can be created concurrently, without blocking writes to the table.
  • You can watch the autovacuum daemon work in pg_stat_activity, and it records what it has done in views such as pg_stat_user_tables.
  • Tables and indexes can have a FILLFACTOR that allows better clustering when inserting data out of order.
  • The seq_page_cost configuration parameter was added, allowing easier fine tuning of how expensive the query...