pg_activity is a top like application for PostgreSQL server activity monitoring.
[header]
section of the configuration file.${XDG_CONFIG_HOME:~/.config}/pg_activity/<profile>.conf
or /etc/pg_activity/<profile>.conf
as selected from the command line through --profile <profile>
.
Some built-in profiles are distributed with pg_activity.K
action, displayed in the footer, has been rephrased as "terminate underlying session".--no-{inst,sys,proc}-info
options and group them into a dedicated section of --help
output.README
.Full Changelog: https://github.com/dalibo/pg_activity/compare/v3.4.2...v3.5.0
tests
and docs
directories
(#378).Full Changelog: https://github.com/dalibo/pg_activity/compare/v3.4.1...v3.4.2
Full Changelog: https://github.com/dalibo/pg_activity/compare/v3.4.0...v3.4.1
client
column by possibly abbreviating IP
addresses.${XDG_CONFIG_HOME:~/.config}/pg_activity.conf
or
/etc/pg_activity.conf
.hidden = yes|no
option).width = <positive integer>
option).Full Changelog: https://github.com/dalibo/pg_activity/compare/v3.3.0...v3.4.0
Handle conversion between PostgreSQL encoding names and Python ones while
decoding the query
column from pg_stat_activity
with
pg_database.encoding
(#348).
Fix typos in man pages, spotted by codespell.
When using the psycopg backend, set client_encoding
to auto
if unspecified
in the connection string. This will help getting the appropriate client
encoding from locale settings, even if the connection database has a different
one.
Fall back to a permissive-but-hopefully-more-robust loader for character type
values if client encoding is really ascii
, when using the psycopg backend.
Add compatibility with old humanize (>= 0.5.1), to make packaging easier on old platforms such as RHEL 8.
Adjust log messages prefix, removing the "Hint" word and adding the level name, as we now emit messages for different purposes.
pip
are encouraged to install the
psycopg
dependency instead of psycopg2.psycopg
and psycopg2
setuptools extras to ease complete installation
from pip.psycopg
database driver for
better performance.query
column to (hopefully) make it more robust
(see #149 for the original report, #302 for a new problem raised while fixing
the previous one and #332 for the latest update).