On Thu, Jul 18, 2024 at 02:24:23PM +0300, Aleksander Alekseev wrote:
> I vaguely recall that I faced this problem before. Supporting crc32
> was requested on the mailing list [2] and a number of workarounds
> exist in PL/pgSQL [3][4]. Since there seems to be a demand and it
> costs us nothing to maintain crc32() I suggest adding it.
This sounds generally reasonable to me, especially given the apparent
demand. Should we also introduce crc32c() while we're at it?
--
nathan