Package: postgresql-10-pg-checksums
Source: pg-checksums
Version: 1.1-6.pgdg20.04+1
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 75
Depends: libc6 (>= 2.17), postgresql-10
Recommends: pg-checksums-doc
Homepage: https://github.com/credativ/pg_checksums
Priority: optional
Section: database
Filename: pool/main/p/pg-checksums/postgresql-10-pg-checksums_1.1-6.pgdg20.04+1_amd64.deb
Size: 30856
SHA256: 57ec3e0e291adf1a42221a00c8c007577d52aa1ffc2eb0aa399ae1ebc22c5672
SHA1: d3ec9cdd086cb14207dc03981a50898b20ea7711
MD5sum: 46133f5ae280a80ddf38700ac0028e87
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.