Package: postgresql-14-pg-checksums
Source: pg-checksums
Version: 1.4-1.pgdg22.04+3
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 89
Depends: postgresql-14, libc6 (>= 2.34)
Recommends: pg-checksums-doc
Homepage: https://github.com/credativ/pg_checksums
Priority: optional
Section: database
Filename: pool/main/p/pg-checksums/postgresql-14-pg-checksums_1.4-1.pgdg22.04+3_amd64.deb
Size: 36128
SHA512: 3f0306c8f70984798981f9d5e74c666f3d47c726c2e7dfcbedaf3b38ac51fbc2f7dce4099d76a9a393ce7e9b999c747c99181e6980b0f570836b066ce34c92ec
SHA256: 2175850f5073d2079ab0a4fa381a76c2bd27edfab8ef0cbbee1d1cb86ea17317
SHA1: 62ebd970dccd7fc892bdf8ee175ee90d4da0e1f1
MD5sum: 7b6d4b178b7422cbb77749f02d7c5ad6
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.