From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: allow frontend use of the backend's core hashing functions |
Date: | 2020-02-14 16:29:01 |
Message-ID: | 20200214162901.GW24870@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 14, 2020 at 08:16:47AM -0800, Mark Dilger wrote:
> > On Feb 14, 2020, at 8:15 AM, David Fetter <david(at)fetter(dot)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(dot)dilger(at)enterprisedb(dot)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?
I hadn't planned on changing the representation, just cutting
instructions out of the calculation of same.
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Dilger | 2020-02-14 16:37:40 | Re: allow frontend use of the backend's core hashing functions |
Previous Message | Robert Haas | 2020-02-14 16:21:37 | Re: allow frontend use of the backend's core hashing functions |