Repository Issue Activity (beta)

#886 Wrong queries dropped when filtering with --dbuser

#885 Multi line statement truncated in report

#882 Use of uninitialized value in pattern match (m//) at /usr/bin/pgbadger line 21785

#881 The way how --explode handles output is problematic

#880 Combination of -E and -R breaks retention

#878 calendar indexes are empty with `--explode`

#877 pgbadger report not returning any queries

#876 Feature: connections per host time series

#875 Use of uninitialized value in pattern match (m//) at /usr/bin/pgbadger line 22471, line 122

#874 Data not showing for Checkpoints

#136 Server side cursor query execution time

#872 Add easy comparation of queries between reports

#873 pgbadger with --exclude-db fails on multi-line log entries

#871 Use of uninitialized value in pattern match (m//) at ./pgbadger line 22471.

#870 Feature : Adding include-app, include-db and include-user

#869 Doc - Wrong example for exclude-db arg ?

#863 breakage under perl-5.42 due to "Possible precedence problem between ! and %s"

#859 Question - How does pgbadger handles the presence of binary inside the log file ?

#804 pgBadger 12.2 - Normalization does not handle properly balanced single-quoted strings along with escaped quotes inside

#868 FATAL: unable to detect log file format from postgres.log, please use -f option

#782 bug with --explode option

#770 can not load incompatible binary data, binary file is from version < 4.0.

#843 datetime parse doesn't work properly

#844 CloudNativePG query logs cannot be parsed if the query contains JSON

#848 Duplicate Query Count When log_statement and auto_explain Are Both Enabled