Re: Drop one-argument string_agg? (was Re: string_agg delimiter having no effect with order by) - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Drop one-argument string_agg? (was Re: string_agg delimiter having no effect with order by)
Date
Msg-id AANLkTikWGuZ_sbqGne8jdHRY_dZMM=YMu4-Dvtcy-HFd@mail.gmail.com
Whole thread Raw
In response to Re: Drop one-argument string_agg? (was Re: [BUGS] string_agg delimiter having no effect with order by)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] Re: Drop one-argument string_agg? (was Re: string_agg delimiter having no effect with order by)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Aug 4, 2010 at 11:19 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> What we are doing here, IMO, is not just changing string_agg() but
> instituting a project policy that we are not going to offer built-in
> aggregates with the same names and different numbers of arguments ---
> otherwise the problem will come right back.

Well I think this can be a pretty soft policy. The thing is that for
string_agg it's a pretty weak argument for the one-argument form
anyways so there's not much loss in losing the 1-argument form. In
other cases the extra arguments might be for very obscure cases or
there may be lots of precedent for the variadic form and users might
expect to have it. In which case we could decide the cost/benefit
calculation comes down the other way.

-- 
greg


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: patch for contrib/isn
Next
From: Robert Haas
Date:
Subject: Re: more numeric stuff