apache2buddy
apache2buddy (by richardforth)
pgbadger
A fast PostgreSQL Log Analyzer (by darold)
Our great sponsors
| apache2buddy | pgbadger | |
|---|---|---|
| 1 | 6 | |
| 380 | 3,373 | |
| - | - | |
| 3.4 | 7.9 | |
| 9 months ago | about 1 month ago | |
| Perl | Perl | |
| Apache License 2.0 | PostgreSQL License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
apache2buddy
Posts with mentions or reviews of apache2buddy.
We have used some of these posts to build our list of alternatives
and similar projects.
pgbadger
Posts with mentions or reviews of pgbadger.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-11.
-
Site down due hosted on digitalocean
It might also help to use pgbadger or something similar to process your postgres logs and see whether some event is aligned with your outages.
-
SQL: 2023 Has Been Released
Interestingly, when a place does get to the point where the single instance has capacity issues (after upgrading to EPYC and lots of flash drives) then other non-obvious stuff shows up too.
For example, at one place just over a year ago they were well into this territory. One of weird problems for them was with pgBadger's memory usage (https://github.com/darold/pgbadger). That's written in perl, which doesn't seem to go garbage collection well. So even on a reporting node with a few hundred GB's of ram, it could take more than 24 hours to do a "monthly" reporting run.
There wasn't a solution in place at the time I left, so they're probably still having the issue... ;)
- Moving from Oracle to Postgres, what should I know?
-
What are the top 3 most useful things that you have hosted over the years?
First of all I used a profiler (pgbadger and netdata) to figure out where the lags were coming from. I then tried the usual stuff (increasing shared_buffers, max_wal_size, min_wal_size from their ultra low defaults), but the biggest performance gain came from moving the database from eMMC to a mechanical hard drive :-D
-
Best way to find queries that might benefit from indexes.
Look into PgBadger (a log parser/analyser): https://github.com/darold/pgbadger
What are some alternatives?
When comparing apache2buddy and pgbadger you can also consider the following projects:
postgresqltuner - Simple script to analyse your PostgreSQL database configuration, and give tuning advice
pgaudit_analyze - PostgreSQL Audit Analyzer