Package: postgresql-17-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: 101
Depends: postgresql-17, 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-17-pg-checksums_1.4-1.pgdg26.04+2_amd64.deb
Size: 37208
SHA512: aa8d73159ae6f79f8c470e1f6034e0f8b0e63b281645f015ca167ffc34e36695d49c6bacc67b7759bd24da6d389dd2a0af67ca563f0e350e9f916f91f548652c
SHA256: 9ab6b4f771707545fad1854fa381e27e7d17aa8f9e00f01105b3fc6e7a2ca094
SHA1: 0f6d443e0359541ad10f237179de4cd198b91af4
MD5sum: 199b6ada01447fa5a42acb501ded651d
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.