Package: postgresql-19-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: 107
Depends: postgresql-19, 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-19-pg-checksums_1.4-1.pgdg22.04+2_amd64.deb
Size: 41676
SHA512: e2001c12c08495d73de6699f356358a49c90bc6b20b31e799534036af12f2a96b465cf4a22206ab2cb1e29b9ad1dad7af69d72b40d95290e50df920dce39448d
SHA256: cbadc18f956bb7e33d605d74be108251242b04bf456ceb0b0cc592edee629d82
SHA1: e5aa3f1edfd8926bc13e6c1dbc45efca73d23a74
MD5sum: 47b4f4f3859bbb6bdcc7aa07e1961ab5
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.