Re: allow frontend use of the backend's core hashing functions - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: allow frontend use of the backend's core hashing functions
Date
Msg-id 68EB30F4-D14C-48F4-AAC7-A4D83EDACE4D@enterprisedb.com
Whole thread Raw
In response to Re: allow frontend use of the backend's core hashing functions  (David Fetter <david@fetter.org>)
Responses Re: allow frontend use of the backend's core hashing functions
List pgsql-hackers

> On Feb 14, 2020, at 8:15 AM, David Fetter <david@fetter.org> wrote:
>
> On Fri, Feb 14, 2020 at 10:33:04AM -0500, Robert Haas wrote:
>> On Thu, Feb 13, 2020 at 11:26 AM Mark Dilger
>> <mark.dilger@enterprisedb.com> wrote:
>>> I have made these changes and rebased Robert’s patches but
>>> otherwise changed nothing.  Here they are:
>>
>> Thanks. Anyone else have comments? I think this is pretty
>> straightforward and unobjectionable work so I'm inclined to press
>> forward with committing it fairly soon, but if someone feels
>> otherwise, please speak up.
>
> One question. It might be possible to make these functions faster
> using compiler intrinsics. Would those still be available to front-end
> code?

Do you have a specific proposal that would preserve on-disk compatibility?

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company






pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: allow frontend use of the backend's core hashing functions
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager