Package: postgresql-18-pg-checksums
Source: pg-checksums
Version: 1.3-2.pgdg26.04+1
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 102
Depends: postgresql-18, 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-18-pg-checksums_1.3-2.pgdg26.04+1_amd64.deb
Size: 38244
SHA256: a9b7a60e42c14b23f83f6a3c74caf3cd01f49bb19f21b5c0a184b3a7712e157e
SHA1: 735e89c451cd4bb19f045c59e6e580fed23f7b6d
MD5sum: 1f0b5a366d77fdea3a2be7af41893cf8
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.