Re: Proposal for enabling auto-vectorization for checksum calculations
Oleg Tselebrovskiy <o.tselebrovskiy@postgrespro.ru>
From: Oleg Tselebrovskiy <o.tselebrovskiy@postgrespro.ru>
To: John Naylor <johncnaylorls@gmail.com>
Cc: Andrew Kim <tenistarkim@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-01-16T04:22:10Z
Lists: pgsql-hackers
Thursday, January 15, 2026 17:35 +07, John Naylor <johncnaylorls@gmail.com> wrote: >External programs are probably doing some one-off task, so I don't see >a reason to work harder. Well, yeah, I agree. I was mostly thinking about some backup tools that could use pg_checksum_page. With a quick search I've found only [1], though. >> Also, not moving all those checksum files to src/port saves us from >> thinking about problems with meson and current external programs, >> but, I think, that after hardware checks are refactored, we could >> revisit the question of moving checksum[_impl].h/.c to src/port. > >Refactoring the hardware checks is not going to make those two >problems go away, and I don't understand why you want to move anything >to begin with. Yeah, moving checksum files to src/port introduces those two problems, and I don't think there is any serious upside in doing this. There was some discussion about it during v5 and v6, but as of v10, this is not needed. [1] - https://github.com/ossc-db/pg_rman -- Regards, Oleg
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Use AVX2 for calculating page checksums where available
- 5e13b0f24039 19 (unreleased) landed
-
Refactor checksumming code to make it easier to use externally.
- f04216341dd1 9.3.0 cited