Package: pg-checksums-doc
Source: pg-checksums
Version: 1.4-1.pgdg26.04+2
Architecture: all
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 14
Multi-Arch: foreign
Homepage: https://github.com/credativ/pg_checksums
Priority: optional
Section: doc
Filename: pool/main/p/pg-checksums/pg-checksums-doc_1.4-1.pgdg26.04+2_all.deb
Size: 5640
SHA512: 8a5e44d658de857330b94c39bf6426996557ccf38b8bc7c56962accb3842bec74c4a345fdd6dbec201d2e0131ae5b09374fa5769359429be030b51d655fe3405
SHA256: 21490345c0c2d9ffa607f58ac9c0134cd3c8b48ff7789eae69230feff057078d
SHA1: 00b749dbfa2a0e9c06ba3aa18c89017c6fa5a809
MD5sum: 8cd03bfa7b68b7b8340e4a2b5b5a4103
Description: Activate/deactivate/verify PostgreSQL data checksums (Documentation)
 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.
 .
 This package contains the manpage.