Re: Fix hashchar() and hashcharextended() to not depend on char signedness

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Tristan Partin <tristan(at)partin(dot)io>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: malis(at)pgrust(dot)com
Subject: Re: Fix hashchar() and hashcharextended() to not depend on char signedness
Date: 2026-08-05 15:47:32
Message-ID: d5a742ec-5abd-4c74-bd4e-a67b5e1cb1bd@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30.07.26 08:51, Tristan Partin wrote:
> In bug #19587[0], the user reported that hashchar() and
> hashcharextended() were not producing the same results for the same
> input because of sign extension depending on the platform.

Is there any claim that data type hash functions are platform-independent?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2026-08-05 15:50:53 Re: BUG: ReadStream look-ahead exhausts local buffers when effective_io_concurrency>=64
Previous Message Matthias van de Meent 2026-08-05 15:31:03 Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object