Re: Proposal for enabling auto-vectorization for checksum calculations - Mailing list pgsql-hackers

From Oleg Tselebrovskiy
Subject Re: Proposal for enabling auto-vectorization for checksum calculations
Date
Msg-id 1768537330.605656780@fmail1.qdit
Whole thread Raw
In response to Re: Proposal for enabling auto-vectorization for checksum calculations  (John Naylor <johncnaylorls@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] pl: fix can not build free-thread for plpython extension like 3.14t
Next
From: jian he
Date:
Subject: Re: using index to speedup add not null constraints to a table