Package: postgresql-15-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: 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+1_amd64.deb
Size: 35020
SHA512: b7be9821d75177030afea5d6fd42874c94228d5d15fb59c1f9fe0e86eddc134cbb1cd29603833d8f490f92b38bbfccb6fe58400fb1142f414f1e7a6b6f1153a5
SHA256: d05d9e4e5214ec2a63b34addb6764a2942718bed515df922c6f32a115e522310
SHA1: f63b495e52bcb6ac80dd1927636aae094db7bcda
MD5sum: 15287d124b08be28a4d5b17737003df6
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.