Horton
Menu

Re: Proposal for enabling auto-vectorization for checksum calculations

John Naylor <johncnaylorls@gmail.com>

View thread
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: 2026-01-13T05:07:13Z
Lists: pgsql-hackers 
On Tue, Jan 13, 2026 at 8:58 AM Andrew Kim <tenistarkim@gmail.com> wrote:
> The removal of the backend-side checksum_backend_lib stanza without an
> equivalent dependency path explains the CI breakage clearly,
> and your diagnosis makes sense, v10-0003 approach,
> splitting the body of checksum_block into a semi-private
> implementation header while preserving the externally visible
> interface,
> that makes sense to me

Glad to hear it.

> I’m supportive of using v10 as the basis for further discussion and iteration,
> cleaning up Meson dependency declarations so generated headers are
> properly ordered,
> refining the PG_CHECKSUM_INTERNAL usage if needed,

Great!

It sounds like you've found some issues to address? It's not clear.

-- 
John Naylor
Amazon Web Services

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Use AVX2 for calculating page checksums where available

  2. Refactor checksumming code to make it easier to use externally.