Book Image

PostgreSQL 10 High Performance - Third Edition

By : Enrico Pirozzi
Book Image

PostgreSQL 10 High Performance - Third Edition

By: Enrico Pirozzi

Overview of this book

PostgreSQL database servers have a common set of problems that they encounter as their usage gets heavier and requirements get more demanding. Peek into the future of your PostgreSQL 10 database's problems today. Know the warning signs to look for and how to avoid the most common issues before they even happen. Surprisingly, most PostgreSQL database applications evolve in the same way—choose the right hardware, tune the operating system and server memory use, optimize queries against the database and CPUs with the right indexes, and monitor every layer, from hardware to queries, using tools from inside and outside PostgreSQL. Also, using monitoring insight, PostgreSQL database applications continuously rework the design and configuration. On reaching the limits of a single server, they break things up; connection pooling, caching, partitioning, replication, and parallel queries can all help handle increasing database workloads. By the end of this book, you will have all the knowledge you need to design, run, and manage your PostgreSQL solution while ensuring high performance and high availability
Table of Contents (18 chapters)

Graphing results with pgbench-tools

Running a full, thorough pgbench evaluation of a server takes several days of system runtime. Starting with PostgreSQL 8.3, the pgbench-tools program, available from http://git.postgresql.org/gitweb?p=pgbench-tools.git, allows for automating multiple runs of pgbench, including production of graphs showing the results. Earlier PostgreSQL versions did not save all of the needed information to allow for graphing results over time.

On a system that supports running the git version control software, you can retrieve the source code like this:

$ git clone git://git.postgresql.org/git/pgbench-tools.git 
$ cd pgbench-tools/ 

If you're on a database server that doesn't support running git, you may need to run the preceding mentioned command on a newer system that does, then use that system to create an archive; here are two examples that produce...