Package: pg-checksums-doc
Source: pg-checksums
Version: 1.4-1.pgdg22.04+2
Architecture: all
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 16
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.pgdg22.04+2_all.deb
Size: 7436
SHA512: 52e508191dad8d0415109ee0c83a446eb5a8eb6bc92c84f4ef5f9b8e7dded993606aea7aa2c0d324f901779815d8fa79f7c32e66a43cdb0bb6069b804628858f
SHA256: 5e486e09146174933a491a67979823e24be92e544b022fbbb422a135c94e6bcb
SHA1: 9fadf3ce8a46f9dc54e1154e698a7b25904591c0
MD5sum: 841167caf1b8a54414d7447105d3c74e
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.