Package: postgresql-19-pg-checksums
Source: pg-checksums
Version: 1.4-1.pgdg22.04+1
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+1_amd64.deb
Size: 41688
SHA512: 709b9fad7a521319a7745fdf509ddd5f88d3664c1978b0c9d45f27d76790c34e2234beeee559ddd337a6e2f8ea602b5960acacf241087719bfe60186dd409d43
SHA256: 06181b0748c710d9fd84f4ee929b9cc31e3c79b52aa76e810a8805ee8b0c2c03
SHA1: 53d1ce84eeb0ad1eddbb89e0bd605637b661379f
MD5sum: 7c109ba486867dff43042144ec513145
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.