Cool development. Great to have it handy in the toolbox. I still have two concerns when simulating a workload in order to test configurations / DDL changes: -

Cool development. Great to have it handy in the toolbox. I still have two concerns when simulating a workload in order to test configurations / DDL changes: - Processing the logs implies generating all for every query that arrives. While this may be acceptable for some cases, it is unacceptable for high volume sites. Logging every query may bring the db down. PostgreSQL needs a different mechanism to report this information, like a streamed UDP of query performance metrics. - Independently, this only reproduces the read workload, but what about the write one? Ideally, you should combine both. Write one may be very well captured and replayed using logical decoding / replication. But still would need a lot of coordination / tooling with the read replaying tool to achieve the desired effect. All in all, complex problems but very important and interesting :)