1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
Source: pgreplay
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Uploaders: Cyril Bouthors <cyb@debian.org>,
Andreas Tille <tille@debian.org>
Section: admin
Priority: optional
Build-Depends: libpq-dev,
debhelper-compat (= 13),
postgresql
Standards-Version: 4.7.2
Vcs-Browser: https://salsa.debian.org/postgresql/pgreplay
Vcs-Git: https://salsa.debian.org/postgresql/pgreplay.git
Homepage: https://laurenz.github.io/pgreplay/
Package: pgreplay
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends}
Description: replay PostgreSQL log files
Reads a PostgreSQL log file (*not* a WAL file), extracts the SQL
statements and executes them in the same order and with the original
timing against a PostgreSQL database.
.
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.
.
A final report gives you a useful statistical analysis of your workload
and its execution.
.
The idea is to replay a real-world database workload as exactly
as possible.
.
This is useful for performance tests, particularly in the following
situations:
- You want to compare the performance of your PostgreSQL application on
different hardware or different operating systems.
- You want to upgrade your database and want to make sure that the new
database version does not suffer from performance regressions that
affect you.
|
