Package: postgresql-13-pg-checksums Source: pg-checksums Version: 1.3-2.pgdg26.04+1 Architecture: amd64 Maintainer: Debian PostgreSQL Maintainers Installed-Size: 88 Depends: postgresql-13, libc6 (>= 2.38) 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.3-2.pgdg26.04+1_amd64.deb Size: 35236 SHA256: cc3f96342e9e987a6baa2120f17c13553f18036962cd6b941e4f7a6747a352ec SHA1: 772c5c0cf634b96c56c74798076316538f2b766c MD5sum: 51da6a4ead31eef952e3aa8231f55593 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.