Package: postgresql-15-pg-checksums
Source: pg-checksums
Version: 1.4-1.pgdg26.04+2
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 85
Depends: postgresql-15, 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-15-pg-checksums_1.4-1.pgdg26.04+2_amd64.deb
Size: 35056
SHA512: ff6c70cdf6fd7b6c7aaff60860e3660d268408e6ae8115178713a91022633dbd836ecaf2a7ac8d33dd425f15ce4ea9a75ca40c30b18c572d81150c2e80e43fa4
SHA256: dba0ba39ed51eb91d38eafe097460963c990a6cfa4f7d340ab994d10d15edfd7
SHA1: e2d9ab18d9223bafe962ca8c17fb144fb2412284
MD5sum: 1b706397b45df06842bc6c5b3728e5dc
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.