pgreplay 1.2.0-2.1 source package in Ubuntu

Changelog

pgreplay (1.2.0-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Convert to 3.0 source format (closes: #1007673).
  * d/copyright: Convert to machine-readable format.

 -- Bastian Germann <email address hidden>  Sat, 03 Dec 2022 01:32:14 +0100

Upload details

Uploaded by:
Cyril Bouthors
Uploaded to:
Sid
Original maintainer:
Cyril Bouthors
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
pgreplay_1.2.0-2.1.dsc 1.6 KiB 1a33dc7e7f784ac15d28e94de0453febfccc798257b44ae463e2296d9929d917
pgreplay_1.2.0.orig.tar.gz 117.3 KiB 9bb050679f1855eb48b61a50d044faf7a33e9dff0ded582a62d7d33f3b0b7328
pgreplay_1.2.0-2.1.debian.tar.xz 2.4 KiB 0741a906cea37359905a7eac38bd8b2e3786de73af2096faf04e11ac80d59134

No changes file available.

Binary packages built by this source

pgreplay: 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.

pgreplay-dbgsym: debug symbols for pgreplay