Package: postgresql-11-pg-checksums
Source: pg-checksums
Version: 1.1-4.pgdg18.04+1
Architecture: i386
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 74
Depends: postgresql-11, libc6 (>= 2.17)
Recommends: pg-checksums-doc
Homepage: https://github.com/credativ/pg_checksums
Priority: optional
Section: database
Filename: pool/main/p/pg-checksums/postgresql-11-pg-checksums_1.1-4.pgdg18.04+1_i386.deb
Size: 32904
SHA256: a6eb381c0bd08154306ae3a76bb61c9b1b424ebbc101404ead6b5d2a99f5427f
SHA1: ea4158ad9550189c9bd12973f1bb8c90c199996f
MD5sum: ffd76b0dcca2fcef8a050282b915fa56
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.