pgreplay

pgreplay parses not the WAL Write Ahead Log but the log file, " extracts the SQL statements and executes them in the same order and relative time against a PostgreSQL database cluster": https://github.com/laurenz/pgreplay "A PostgreSQL Docker container that automatically upgrades your database" (2023) https://news.ycombinator.com/item?id=36748041 : pgkit wraps Postgres PITR backup and recovery: https://github.com/SadeghHayeri/pgkit#pitr : $ sudo pgkit pitr backup <name> <delay> $ sudo pgkit pitr recover <name> <time> $ sudo pgkit pitr recover <name> latest

Hey, author here! Perhaps I'm missing something, but I think pgBadger is just for log analysis, no? pgBadger is the second component to the tool this article is about. The idea is to replay the original production logs and capture the target clusters logs while you do it. After the benchmark is complete you can pass the logs into pgBadger to understand what happened with the performance, and compare the report to one produced for production. I hadn't come across nancy before though, this looks cool! For replay of real logs nancy appears to use the original pgreplay (https://github.com/laurenz/pgreplay) so it would have been subject to the same issue that motivated building pgreplay-go, but I bet providing an option to switch between the tools would be quite easy.