Package: postgresql-15-pg-checksums
Source: pg-checksums
Version: 1.4-1.pgdg22.04+2
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+2_amd64.deb
Size: 36580
SHA512: 9885fed3baed43b9684027ddfca74841b39e1de860a0766d501d5bea6870a00cbbd194e3e993a456606354d03bbc6700c28c58cfb1218c1e10e2cfbe9278de73
SHA256: 7f49c2b17d36e4edd4f6d93d94b612adbb528c8e2b6e562678c860230b9a8129
SHA1: 55b5c6df978fa158c4996e69bfb5aea179f6ed4b
MD5sum: 7b7e202288e4cb65bc20d662d4af3ae2
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.