Re: Adding argument names to aggregate functions - Mailing list pgsql-hackers

From Vik Fearing
Subject Re: Adding argument names to aggregate functions
Date
Msg-id 3c173b2c-4a12-d398-6bf1-c48080541a42@postgresfriends.org
Whole thread Raw
In response to Adding argument names to aggregate functions  (Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>)
List pgsql-hackers
On 2/27/23 14:22, Dagfinn Ilmari Mannsåker wrote:
> Hi hackers,
> 
> I'm sure I'm not the only one who can never remember which way around
> the value and delimiter arguments go for string_agg() and has to look it
> up in the manual every time. To make it more convenient, here's a patch
> that adds proargnames to its pg_proc entries so that it can be seen with
> a quick \df in psql.
> 
> I also added names to json(b)_object_agg() for good measure, even though
> they're more obvious. The remaining built-in multi-argument aggregate
> functions are the stats-related ones, where it's all just Y/X (but why
> in that order?), so I didn't think it was necessary. If others feel more
> strongly, I can add those too.

No comment on adding names for everything, but a big +1 for the ones 
included here.
-- 
Vik Fearing




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)
Next
From: Michael Paquier
Date:
Subject: Re: Provide PID data for "cannot wait on a latch owned by another process" in latch.c