Package: postgresql-15-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: 87
Depends: postgresql-15, 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-15-pg-checksums_1.4-1.pgdg22.04+1_amd64.deb
Size: 36560
SHA512: 3941f0364ae4fe4dcab100a12adf5060cf0fcd3dcccfffe44377b25c7d00f0847367318121efb6881118d33402f5f4fca1cd875c4df64fb3a854de583fe01584
SHA256: ae1ec91016e51f9c74f4b03ee83c3e27a1a3df4cfe241caea28a2eba7f2950fd
SHA1: f466ede4325ad47c6736c6d050e5389041ca7e64
MD5sum: fe0db84dbdbf1d72a3b4a98ebeda916d
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.