Re: Aggregate versions of hashing functions (md5, sha1, etc...)

From: Dominique Devienne <ddevienne(at)gmail(dot)com>
To: Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Aggregate versions of hashing functions (md5, sha1, etc...)
Date: 2025-07-11 16:16:59
Message-ID: CAFCRh-_3oKeCDKOFWQ=bxBPNZWtrvL1ucG5wjOxh2HgEbz-qtw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jul 11, 2025 at 6:05 PM Florents Tselai
<florents(dot)tselai(at)gmail(dot)com> wrote:
> On Fri, Jul 11, 2025, 18:27 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>> [...] create an extension that incorporates the code.
>
> That's an ideal use case for an extension indeed .

Extensions are of no use to me, unfortunately, unless built-in and
official. So if I have to wait for v19, so be it. But the ball has to
get rolling at least.

And extensions address only the missing aggregate "overloads". Not the
fact current md5() and pgcrypto.digest() are not TOAST-aware to be
"really streaming", and low-memory.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Edmundo Robles 2025-07-11 17:12:38 I have a suspicious query
Previous Message Adrian Klaver 2025-07-11 16:15:28 Re: Aggregate versions of hashing functions (md5, sha1, etc...)