Re: Proposal for enabling auto-vectorization for checksum calculations

John Naylor <johncnaylorls@gmail.com>

From: John Naylor <johncnaylorls@gmail.com>

To: Andrew Kim <tenistarkim@gmail.com>

Cc: pgsql-hackers@lists.postgresql.org, Oleg Tselebrovskiy <o.tselebrovskiy@postgrespro.ru>

Date: 2025-10-29T02:50:45Z

Lists: pgsql-hackers

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

On Fri, Oct 24, 2025 at 2:49 PM Andrew Kim <tenistarkim@gmail.com> wrote:
> The function signatures (pg_checksum_block, pg_checksum_page) remain
> identical, and checksum_impl.h still contains the complete
> implementation that external programs can include. The runtime
> dispatch only affects internal PostgreSQL usage.

I don't quite understand the architecture here -- all
platform-specific definitions were put in the "checksum_impl.h"
header. My thinking was that checksum.c would have all that, with thin
wrappers around the functions included from that header.

--
John Naylor
Amazon Web Services