pg_verify_checksums review
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t38885psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 27, 2026 at 08:16 PM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t38885_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t38885_1 && git checkout t38885_1Patchset v1 (message #1) is on t38885_1
In looking over pg_verify_checksums I found a few small things that I think
would improve on it:
* pg_verify_checksums was placed in the Client Utils section in the docs.
Since it requries physical access to the cluster datafiles it seems to belong
in the Server Utils section.
* The -D option and supported environment variable wasn’t documented.
* Only -D is supported for specifying the data directory, but most all other
utilities also support --pgdata on top of -D. To present a consistent user
interface we should probably support --pgdata in pg_verify_checksums as well.
The latter is I assume too invasive as we are past the freeze, but the first
two docs patches would make sense in 11 IMO as they document whats in the tree.
The attached patches fixes the above mentioned things (I don’t have a docs
toolchain working right now so the docs patches are best effort).
cheers ./daniel
Attachments:
t38885_10001-Move-pg_verify_checksum-from-client-to-server-utils.patchapplication/octet-stream; name=0001-Move-pg_verify_checksum-from-client-to-server-utils.patch; x-unix-mode=0644Download+1-2
0002-Add-D-option-to-pg_verify_checksum-documentation.patchapplication/octet-stream; name=0002-Add-D-option-to-pg_verify_checksum-documentation.patch; x-unix-mode=0644Download+26-1
0003-Add-pgdata-as-alias-for-D-for-consistency.patchapplication/octet-stream; name=0003-Add-pgdata-as-alias-for-D-for-consistency.patch; x-unix-mode=0644Download+14-8
On Tue, Jun 19, 2018 at 10:25 AM, Daniel Gustafsson <daniel@yesql.se> wrote:
In looking over pg_verify_checksums I found a few small things that I think
would improve on it:* pg_verify_checksums was placed in the Client Utils section in the docs.
Since it requries physical access to the cluster datafiles it seems to
belong
in the Server Utils section.
Makes sense.
* The -D option and supported environment variable wasn’t documented.
* Only -D is supported for specifying the data directory, but most all
other
utilities also support --pgdata on top of -D. To present a consistent user
interface we should probably support --pgdata in pg_verify_checksums as
well.
The latter is I assume too invasive as we are past the freeze, but the
first
two docs patches would make sense in 11 IMO as they document whats in the
tree.The attached patches fixes the above mentioned things (I don’t have a docs
toolchain working right now so the docs patches are best effort).
I believe both those are fine for 11, so I've pushed that. I kept it as a
separate patch to make it easy enough to revert it if people prefer that :)
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
Hello,
There is a similar utility that I wrote that does offline checksum
verification as well.
https://github.com/google/pg_page_verification
This utility includes a verbose option as well as scanning multiple
subsequent segment files.
Alexis
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html