Package: postgresql-16-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: 99
Depends: libc6 (>= 2.17), postgresql-16
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.1-6.pgdg20.04+1_amd64.deb
Size: 36660
SHA256: c35f6aa3a65005d30bd96e1618becfd0ffb32bf8fa421fa19fa7a1aaaeeab3bf
SHA1: 828c35b810e1ce91e68e5e763bff48404b08035b
MD5sum: 6f36b283f3acdf887506d2f53df8c67d
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.