Package: postgresql-18-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: 101
Depends: postgresql-18, 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-18-pg-checksums_1.4-1.pgdg26.04+2_amd64.deb
Size: 37684
SHA512: 7ad8d09cdd6d27678ff6da69d86c48c8b4b1f2bad1cbcf074e0bc425f58b3a24e23dee1749725614f7390e6ff3e0d232f2f1ab9d3279de0788975c557d7c8d31
SHA256: c0bcb0ae190a9b2b96cc961f67ae2d40c3a8bc8d1c44be31d383afcac87f966c
SHA1: 5014b6e96cbf9ba4f4dfea663e21acb3fbcc8118
MD5sum: 4b7f00ab037bd0d15ecc2f88908135ae
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.