Support and Contributing

pgBadger is maintained as an open project. Bug reports, feature proposals, documentation fixes, and patches are handled through the upstream GitHub repository.

Bugs and feature requests

1. Upgrade to the newest released version and confirm the behavior still occurs.
2. Search open issues and closed issues for an existing answer.
3. Reduce the problem to the smallest safe log sample and command line that still reproduces it.
4. Remove credentials, sensitive SQL, bind values, host names, addresses, and business data.
5. Open a new issue with the pgBadger version, operating system, input format, exact options, observed result, and expected result.

For crashes or parser mistakes, include only the minimum sanitized log lines needed to reproduce the boundary. A complete production log or generated report is rarely appropriate for a public issue.

Contribute a patch

The project includes an .editorconfig file for consistent spacing. Keep command help, POD, and generated Markdown documentation aligned when a change affects user-visible behavior.

The upstream documentation workflow is:

$ perl Makefile.PL
$ make README

doc/pgBadger.pod is the primary long-form source. pgbadger --help supplies the synopsis, while the README files are generated views. Run the relevant tests before submitting a pull request.

• Source repository
• Pull requests
• Contribution guide
• Development notes

Commercial support

The pgBadger project does not promise maintenance or support under its license. For paid help with PostgreSQL logging, performance analysis, or report automation, consult the PostgreSQL professional services directory .