Re: Proposal for enabling auto-vectorization for checksum calculations

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: Andrew Kim <tenistarkim(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Oleg Tselebrovskiy <o(dot)tselebrovskiy(at)postgrespro(dot)ru>
Subject: Re: Proposal for enabling auto-vectorization for checksum calculations
Date: 2026-01-13 05:07:13
Message-ID: CANWCAZbjdFnBiUmrBQC5vFFy0Fnn4SJG4AkkzGpTFhovodJdYQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 13, 2026 at 8:58 AM Andrew Kim <tenistarkim(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Steven Niu 2026-01-13 05:33:47 Re: str_casefold: fix typo in error message
Previous Message Tom Lane 2026-01-13 04:40:38 Re: typedef indentation in pg_shmem.h