Package: postgresql-17-pg-checksums
Source: pg-checksums
Version: 1.2-2.pgdg22.04+1
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 103
Depends: libc6 (>= 2.34), postgresql-17
Recommends: pg-checksums-doc
Homepage: https://github.com/credativ/pg_checksums
Priority: optional
Section: database
Filename: pool/main/p/pg-checksums/postgresql-17-pg-checksums_1.2-2.pgdg22.04+1_amd64.deb
Size: 38552
SHA256: 4168a8fd25286eee57bca3720caa3e03c46bc1c603f6d177d996de2dcc63a204
SHA1: e2f286010a3449a28f0cb3a2e6acff1f12492b76
MD5sum: 64a15a115c4aa5ce060c8b32b418bbe6
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.