Re: Add MIN/MAX aggregate support for uuid
Tristan Partin <tristan@partin.io>
From: "Tristan Partin" <tristan@partin.io>
To: "Bharath Rupireddy" <bharath.rupireddyforpostgres@gmail.com>
Cc: "Masahiko Sawada" <sawada.mshk@gmail.com>, "pgsql-hackers"
<pgsql-hackers@postgresql.org>
Date: 2026-06-24T21:26:10Z
Lists: pgsql-hackers
Attachments
- v3-0001-Add-MIN-MAX-aggregate-support-for-uuid.patch (text/x-patch) patch v3-0001
On Wed Jun 24, 2026 at 7:47 PM UTC, Bharath Rupireddy wrote:
> Hi,
>
> On Wed, Jun 24, 2026 at 12:13 PM Tristan Partin <tristan@partin.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.
I ended up just using a similar string as oidlarger and bytea_larger.
Although, I added the word "the" to make the descriptions a little more
readable than their counterparts.
"larger of the two" and "smaller of the two"
--
Tristan Partin
PostgreSQL Contributors Team
AWS (https://aws.amazon.com)
Commits
-
Add min() and max() aggregate support for uuid.
- 2e606d75c0bf master landed