Package: postgresql-17-pg-checksums
Source: pg-checksums
Version: 1.3-2.pgdg26.04+1
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 102
Depends: postgresql-17, 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-17-pg-checksums_1.3-2.pgdg26.04+1_amd64.deb
Size: 37884
SHA256: 1737fc571188c32d19be997aee0e4283e93a098993e3bf9c7431956b24587fa5
SHA1: fc2249312c5a0811a95ef1a43fc548338d49ab00
MD5sum: b7a05db2b9bf59bcea87eeae03e51115
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.