Package: postgresql-19-pg-checksums
Source: pg-checksums
Version: 1.4-1.pgdg26.04+1
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 105
Depends: postgresql-19, libc6 (>= 2.38)
Recommends: pg-checksums-doc
Homepage: https://github.com/credativ/pg_checksums
Priority: optional
Section: database
Filename: pool/main/p/pg-checksums/postgresql-19-pg-checksums_1.4-1.pgdg26.04+1_amd64.deb
Size: 40060
SHA512: db12291df48082714b62b0a8aeb34391c6feaee01bda567d43330d019dda255f2f01bab4124e29537f075249d1f133749c5f9e954044581159ed42c458d69924
SHA256: e6081384fb2c2b121bd15b29fcf7f608f344e26a823dd25462fdf39f4747fec6
SHA1: 1a893b1cd27f460e0b91f50e37fbcdbfd7f627c2
MD5sum: e15ecde4f59b2206b2aeb1c2e16be9ff
Description: Activate/deactivate/verify PostgreSQL data checksums
 Data checksums allow the PostgreSQL database server to identify I/O failures
 when reading data from storage. The checksums stored in the page header of
 each data page are compared to the computed checksum of the read data.
 .
 Data checksums need to be activated at instance creation time, all current
 versions of PostgreSQL including v11 do not allow activating (or deactivating)
 checksums afterwards.
 .
 pg_checksums_ext can activate or deactivate data checksums as long at the
 database cluster is shutdown cleanly. Activating checksums requires all
 database blocks to be read and all page headers to be updated, so can take a
 long time on a large database. Deactivating checksums only requires the
 cluster control file to be updated so is quick.
 .
 In addition, pg_checksums_ext can verify the checksums in an online cluster.