Package: postgresql-13-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: 89
Depends: libc6 (>= 2.17), postgresql-13
Recommends: pg-checksums-doc
Homepage: https://github.com/credativ/pg_checksums
Priority: optional
Section: database
Filename: pool/main/p/pg-checksums/postgresql-13-pg-checksums_1.1-6.pgdg20.04+1_amd64.deb
Size: 36016
SHA256: 4e86ba6cbfe1e2055c7c0abe3a34adb8fc39d6d5a45297512f356baf6e5ae952
SHA1: 87e4637c6cc88eb59564fcb4d42c3cc27c4d3b96
MD5sum: 229f0c53d2732b6ff0a26aceb27a5e79
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.