Skip to content

Latest commit

 

History

History
52 lines (37 loc) · 1.8 KB

README.rst

File metadata and controls

52 lines (37 loc) · 1.8 KB

hppt

High Performance PostgreSQL Tools

Production quality programs for monitoring and tuning a busy PostgreSQL installation. Tools are broken into rep (replication) and perf (performance) directories.

Configuration

The database used for all the perf scripts can be set two ways with environment variables:

export HPPTDATABASE="db01"
export HPPTOPTS="-d db01"

Using HPPTDATABASE is simpler, working like the built-in PGDATABASE environment variable. Using HPPTOPTS instead directly adds entries to the psql command line, allowing you to add any additional information needed for these scripts to run in your environment.

Most scripts will accept the database name when provided on the command line:

perf/long-runners db01

TODO

  • There are some hard-coded things in these programs that should be more flexible input parameters. The model for how everything should look eventually is the fully command line parameterized rep/archive_wal program. Ideally needing to use environment variables for the database to connect to shouldn't even be necessary, if instead you'd prefer to pass options to every script you call.
  • Right now the worst script needing cleanup is rep/restore-archive-file since it has a hard-coded archive directory name with no way to set that. rep/restore-archive-file has a similar issue.
  • Several of the connection monitoring scripts in perf use pg_stat_activity, and they've been split into current >-9.2 and a deprecated 9.1 directory. Ideally there would only be one script and it would detect the server version. Note that this is not the psql version, since the client may be running a different version than the server.

License

Copyright 2013-2016 Gregory Smith [email protected] 2-Clause BSD Licensed; see LICENSE for details.