PostgreSQL Log Analyzer: Slow Queries, Errors and Lock Waits

A small pgBadger-style summary: slow queries by shape, grouped errors, lock waits and deadlocks.

Use the tool

Why this tool exists

Slow query logs list the same query with different literals. Grouping by shape shows which query costs the most in total, not just the slowest single run.

Parsing depends on your log_line_prefix and on log_min_duration_statement or log_duration being set. Multi-line statements are joined. For a real report on large logs use pgBadger.

How to use it

  1. Set log_min_duration_statement and collect the log.
  2. Paste the log or open the file.
  3. Choose how to rank query shapes.
  4. Read slow queries, errors and lock waits.

Frequently asked questions

How are queries grouped?

Literals become ? and the text is lower-cased, so two queries that differ only by values share a shape.

Why do I see no slow queries?

Duration lines appear only when log_min_duration_statement or log_duration is on.

Is it as good as pgBadger?

No. It is a quick view for pasted logs, with no charts and no prepared-statement tracking.

Is my log uploaded?

No. Everything is processed in your browser and nothing is sent. Logs can hold IP addresses and tokens, so the page does not write them into the address bar.