| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Tristan Partin <tristan(at)partin(dot)io> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add MIN/MAX aggregate support for uuid |
| Date: | 2026-06-24 19:47:13 |
| Message-ID: | CALj2ACX+5AfXbo0oPuDmXNvvoR4vGk5qmXqi=3DE8w3GpzZv3Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Wed, Jun 24, 2026 at 12:13 PM Tristan Partin <tristan(at)partin(dot)io> wrote:
>
> Any opinions on what the descriptions should be? Here are the equivalent
> functions for OID:
>
> { oid => '1965', descr => 'larger of two',
> proname => 'oidlarger', prorettype => 'oid', proargtypes => 'oid oid',
> prosrc => 'oidlarger' },
> { oid => '1966', descr => 'smaller of two',
> proname => 'oidsmaller', prorettype => 'oid', proargtypes => 'oid oid',
> prosrc => 'oidsmaller' },
What you have in the v2 patch looks fine to me. "minimum/maximum value
of all UUID input values" gives it a bit of an "aggregate flavor" as
well - as in, when used in select min(uuid_col) from foo, it returns
the minimum value of all UUID input values.
--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2026-06-24 19:48:20 | Re: pg_get__*_ddl consolidation |
| Previous Message | Zsolt Parragi | 2026-06-24 19:31:33 | Re: Proposal: Conflict log history table for Logical Replication |