Package: postgresql-10-pg-checksums
Source: pg-checksums
Version: 1.1-4.pgdg18.04+1
Architecture: i386
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Installed-Size: 74
Depends: postgresql-10, libc6 (>= 2.17)
Recommends: pg-checksums-doc
Homepage: https://github.com/credativ/pg_checksums
Priority: optional
Section: database
Filename: pool/main/p/pg-checksums/postgresql-10-pg-checksums_1.1-4.pgdg18.04+1_i386.deb
Size: 32760
SHA256: 33862231fea7bdac40313be06abd2d2e29dbafed64d948b459c3da2ed405c422
SHA1: ab24f5cf78f7a818950062507f8626632a34f443
MD5sum: e48387b3db119bfb216aec3e35e689f0
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.