Package: postgresql-16-pg-checksums
Source: pg-checksums
Version: 1.4-1.pgdg26.04+2
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 97
Depends: postgresql-16, 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-16-pg-checksums_1.4-1.pgdg26.04+2_amd64.deb
Size: 35280
SHA512: 46a57800141ded1ed3e0387cf5f76e7ae6e146e0c339665642acfad76f04f7feef09a2a5937e45f2fb77c058f9a2dfcce84e109bc9ef6b40a4918f9de234684a
SHA256: 78c60a47169124eea9cb7a75f3f201dbc43a4fde08f1c94004e4b0083187a0a7
SHA1: 1eaca48b8d90f571d16cc09a7b540550098e4f91
MD5sum: a9a08b48fe9676aece8b030728e8a185
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.