pgreplay 1.2.0-2.1build1 source package in Ubuntu

Changelog

pgreplay (1.2.0-2.1build1) noble; urgency=medium

  * No-change rebuild for CVE-2024-3094

 -- William Grant <email address hidden>  Mon, 01 Apr 2024 18:14:26 +1100

Upload details

Uploaded by:
William Grant
Uploaded to:
Noble
Original maintainer:
Ubuntu Developers
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Questing release universe misc
Plucky release universe misc
Oracular release universe misc
Noble release universe misc

Downloads

File Size SHA-256 Checksum
pgreplay_1.2.0.orig.tar.gz 117.3 KiB 9bb050679f1855eb48b61a50d044faf7a33e9dff0ded582a62d7d33f3b0b7328
pgreplay_1.2.0-2.1build1.debian.tar.xz 2.6 KiB 6586b61c03ab29ae0099aba94dd1b2e8e2e1497146034e0649d717aea65d1831
pgreplay_1.2.0-2.1build1.dsc 1.9 KiB de2ac96eeab300ed74254048e2eb351547c4e78d3b6c1c902ee23c86280d7d45

View changes file

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