Package: postgresql-9.6-pg-checksums Source: pg-checksums Version: 1.0-8.pgdg18.04+1 Architecture: i386 Maintainer: Debian PostgreSQL Maintainers Installed-Size: 70 Depends: libc6 (>= 2.4), postgresql-9.6 Recommends: pg-checksums-doc Homepage: https://github.com/credativ/pg_checksums Priority: optional Section: database Filename: pool/main/p/pg-checksums/postgresql-9.6-pg-checksums_1.0-8.pgdg18.04+1_i386.deb Size: 30932 SHA256: 8c40986ae2083b4f5bc4cedabb3491b0b8f6c9133e959b579957005f862ace7b SHA1: 2a16ccc48145d8066d60d62b65aba0e6b0f580ee MD5sum: 29af7647a4953e1225040d48b00c4635 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 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 can verify the checksums in an offline cluster.