Package: postgresql-17-pg-checksums
Source: pg-checksums
Version: 1.3-2.pgdg22.04+1
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 103
Depends: postgresql-17, 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-17-pg-checksums_1.3-2.pgdg22.04+1_amd64.deb
Size: 38396
SHA256: 3eee3979bc370c21b3ac1b2fce0b3aaef11dd2a50d6e39920ab5add2c3089d50
SHA1: 8a9cc04b0c186e1033375f9c2a4e6de7bbeeedbb
MD5sum: 696e1b4de080d40b94db16641ed56667
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.