Package: postgresql-12-pg-checksums Source: pg-checksums Version: 1.1-4.pgdg18.04+1 Architecture: i386 Maintainer: Debian PostgreSQL Maintainers Installed-Size: 88 Depends: postgresql-12, 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-12-pg-checksums_1.1-4.pgdg18.04+1_i386.deb Size: 38116 SHA256: 9c9bd2c7c11817ae5cec776faf18db0734b9b2fe60bf8471483c3c1d3c9b463d SHA1: 90cbdc44b89a9163dd25b156fc6d6b4c02470861 MD5sum: 58f9f3de39898e56a2f31708c7209c68 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.