Package: postgresql-19-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: 105
Depends: postgresql-19, 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-19-pg-checksums_1.4-1.pgdg26.04+2_amd64.deb
Size: 40076
SHA512: 353a756f0ec071182fe1c0e3e68d7dad51cd9727ad331ececf433b7704916497929bf89e16922c955cf358aa74220b3b03fc0b9614e10234e5cd9d90cd483f62
SHA256: 8254fff212e780bf88e46a2b331e1641e490172ee79668a1e9b0cd4e27cfeb1e
SHA1: 79054fb8c947384a30102c8c4da1e6337fd025d1
MD5sum: edf81fe69e1f72905b7c6009922d301e
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.