Package: postgresql-17-pg-crash Source: pg-crash Version: 0.3-2.pgdg26.04+2 Architecture: amd64 Maintainer: Debian PostgreSQL Maintainers Installed-Size: 43 Depends: postgresql-17, libc6 (>= 2.38) Breaks: postgresql-17-jit-llvm (<< 21) Homepage: https://github.com/cybertec-postgresql/pg_crash Priority: optional Section: database Filename: pool/main/p/pg-crash/postgresql-17-pg-crash_0.3-2.pgdg26.04+2_amd64.deb Size: 13424 SHA512: bf4a76fb70698ca71355ad417f29c1d936fffed60b44627ff6b4361e618f9a37ecc194efafae693964de986f07587bea490d6bdad6bd45ab7c793a87e9435f98 SHA256: ff62e7b29202dd8c496092843c5ebfaddc851f2a873ad706b126cdb87290f230 SHA1: a7e029024586f94af63b698210ff9c3f04354210 MD5sum: 4ecdb7295c993b88bf093d42356157e5 Description: Periodically crash your PostgreSQL database If your database is too reliable - pg_crash can kill it for you. pg_crash is an extension to PostgreSQL that periodically crashes your database infrastructure by sending kill (or other) signals to your DB processes and make them fail. It is ideal for HA and failover testing.