From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
Cc: | 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-24 12:02:29 |
Message-ID: | CA+TgmoayKs+zKTau0nAyHa0krVrxV3dLCgH-JbWZU=DfJR1mew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 14, 2020 at 9:03 PM Robert Haas <robertmhaas(at)gmail(dot)com> 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.
I've committed 0001 through 0003 as revised by Mark in accordance with
the comments from Suraj. Here's the last patch again with a tweak to
try not to break the Windows build, per some off-list advice I
received on how not to break the Windows build. Barring complaints
from the buildfarm or otherwise, I'll commit this one too.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment | Content-Type | Size |
---|---|---|
v3-0001-Move-src-backend-utils-hash-hashfn.c-to-src-commo.patch | application/octet-stream | 22.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Knizhnik | 2020-02-24 12:02:44 | Re: Yet another vectorized engine |
Previous Message | Kuntal Ghosh | 2020-02-24 11:21:13 | Re: ALTER TABLE ... SET STORAGE does not propagate to indexes |