Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Supported versions and formats

PostgreSQL14 to 18, each tested against a real server
Log formatsstderr (any log_line_prefix, inferred), csvlog, jsonlog
Compressiongzip, zstd, xz, lz4, bzip2, detected from the file contents
StatisticsCSV exports of pg_stat_statements, pg_stat_statements_info, pg_stat_database and pg_settings, which snap writes beside each other
ExperimentalpgBouncer logs; Portuguese (Brazil), Spanish, French, German servers; clouds other than Amazon RDS
PlatformsLinux and macOS tested in CI; Windows experimental

Multi-line entries, application names with spaces and Amazon RDS truncation markers are handled.

Not read

  • Syslog output and auto_explain plans.
  • Logs on a remote machine, other than through logs fetch (vendor CLIs, or --provider sql for a server that exposes its log directory).
  • A log line, an assembled entry or a csvlog record over 16 MiB: it is skipped and counted in the diagnostics, instead of being read whole into memory. For csvlog, the usual cause is an unterminated quote, and the file stops there.

Output

  • JSON has a schema_version. While pgloupe is before 0.1.0 the schema can change between releases; the changelog says when.
  • CSV is the statement table, with formula-looking cells quoted so a spreadsheet does not run them.
  • HTML is one self-contained file with no network requests.
  • Stores carry a schema version. A store from an older release is refused with a message saying to delete it and ingest again.