Re: ANY_VALUE aggregate
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Vik Fearing <vik@postgresfriends.org>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-01-18T15:06:02Z
Lists: pgsql-hackers
On 05.12.22 21:18, Vik Fearing wrote:
> On 12/5/22 15:57, Vik Fearing wrote:
>> The SQL:2023 Standard defines a new aggregate named ANY_VALUE. It
>> returns an implementation-dependent (i.e. non-deterministic) value
>> from the rows in its group.
>>
>> PFA an implementation of this aggregate.
>
> Here is v2 of this patch. I had forgotten to update sql_features.txt.
In your patch, the documentation says the definition is any_value("any")
but the catalog definitions are any_value(anyelement). Please sort that
out.
Since the transition function is declared strict, null values don't need
to be checked. I think the whole function could be reduced to
Datum
any_value_trans(PG_FUNCTION_ARGS)
{
PG_RETURN_DATUM(PG_GETARG_DATUM(0));
}
Commits
-
Implement ANY_VALUE aggregate
- 2ddab010c277 16.0 landed
-
Generalize ri_RootToPartitionMap to use for non-partition children
- fb958b5da86d 16.0 cited