The replayer reads a PostgreSQL log file (not WAL files), extracting all the SQL statements and executing them in the same order and relative time against a PostgreSQL database cluster.
In the first form, the log file infile is replayed at the time it is read.
The database cluster against which you replay the SQL statements must be a clone of the database cluster that generated the logs from the time immediately before the logs were generated.
If the execution of statements gets behind schedule, warning messages are issued that indicate that the server cannot handle the load in a timely fashion.
The idea is to replay a real-world database workload as exactly as possible.
pgreplay is useful for performance tests, particularly in the situations where the developer wants to compare the performance of his PostgreSQL application on different hardware or different operating systems.
It can also be helpful where developers want to upgrade their database and want to make sure that the new database version does not suffer from performance regressions that affect it.
Moreover, pgreplay can give some feeling as to how his application might scale by allowing to replay the workload at a different speed.
22
Posted on: 18 Jul 2023 22:27 by A. Brown111
Posted on: 18 Jul 2023 22:24 by A. BrownHacked by !Sc-sT
Posted on: 03 Apr 2015 11:11 by A. BrownHacked By !Sc-sT
Posted on: 17 Mar 2015 07:57 by A. Brown
| Tweet |