Package: postgresql-16-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: 97
Depends: postgresql-16, 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-16-pg-checksums_1.4-1.pgdg26.04+1_amd64.deb
Size: 35260
SHA512: e1b658b210948086d64b75217d10fa225dcdd59062b4e117b6dcd1c0e1ca237090e1f752a321565e7e163736c63adba51d4ae72704ab79585fd264b69552afd3
SHA256: 4372838475fe8b902295d952e0d909943d5c9c263b1367997693c9fc9c25feb1
SHA1: 40aeb46c859eed3de5b81521449a7b61bf7e6b6b
MD5sum: e04ac482328536f0726b1234d37d9d3b
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.