Package: postgresql-16-pg-checksums Source: pg-checksums Version: 1.2-2.pgdg20.04+1 Architecture: amd64 Maintainer: Debian PostgreSQL Maintainers Installed-Size: 99 Depends: libc6 (>= 2.17), postgresql-16 Recommends: pg-checksums-doc Homepage: https://github.com/credativ/pg_checksums Priority: optional Section: database Filename: pool/main/p/pg-checksums/postgresql-16-pg-checksums_1.2-2.pgdg20.04+1_amd64.deb Size: 36488 SHA256: 550de95e09bd04fb73d1f1f54f5a3ee247bdbf08505c892fbe91b77a9f6c6759 SHA1: a2288a13a1230f4f81cc3a7378567bac668b39c9 MD5sum: 472282db4820aafbf9cab6818482a66f 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.