Package: postgresql-16-pg-checksums
Source: pg-checksums
Version: 1.4-1.pgdg22.04+2
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 99
Depends: postgresql-16, 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-16-pg-checksums_1.4-1.pgdg22.04+2_amd64.deb
Size: 36988
SHA512: cbfab619df4f2810d78219a4ab5b328fe066ba2a64840a4113963cb9bac0141e52e42a72905bf9e34745fdb639e2a8458f878d50151201115a26aa1cbb888465
SHA256: 388244559e3c1ad8106c5c9058a8f91708483574f88731c4170077aee605f920
SHA1: 33c28355837dafdd7d82699b2b5dc9d02a760960
MD5sum: 9ad7e985a78b7c6c08d1e15de3ec32f2
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.