Package: postgresql-17-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: 103
Depends: postgresql-17, 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-17-pg-checksums_1.4-1.pgdg22.04+2_amd64.deb
Size: 38924
SHA512: dfa37b934fbe09f405f27422efaee11ac5ec2d879e30855a4b763ce9ae513555c8a5178893ed307d418f4ab48a73bbd2732f57568986335d6827ba30954bb1e7
SHA256: 10637e2c242de9c8645f956682880139962658c5a9abc32a68a37bb0c98cbfba
SHA1: bcc0dcf2d2cace4cd91cc99ce9f6703ee7aba786
MD5sum: 827c20c363c29e321396155efdce2f28
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.