Re: [PATCH] Add crc32(text) & crc32(bytea)

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, Aleksander Alekseev <aleksander@timescale.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-08-08T14:49:42Z
Lists: pgsql-hackers
Nathan Bossart <nathandbossart@gmail.com> writes:
> On Thu, Aug 08, 2024 at 04:27:20PM +0200, Peter Eisentraut wrote:
>> The correct return type of a CRC operation in general is some kind of exact
>> numerical type.  Just pick the best one that fits the result.  I don't think
>> bytea is appropriate.

> That would leave us either "integer" or "bigint".  "integer" is more
> correct from a size perspective, but will result in negative values because
> it is signed.  "bigint" uses twice as many bytes but won't display any CRC
> values as negative.

bigint seems fine to me; we have used that in other places as a
substitute for uint32, eg block numbers in contrib/pageinspect.

			regards, tom lane



Commits

  1. Add user-callable CRC functions.

  2. Add user-callable SHA-2 functions