Re: Variadic aggregates vs. project policy

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Variadic aggregates vs. project policy
Date: 2013-08-29 22:44:57
Message-ID: 521FCEE9.1070405@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 08/29/2013 05:37 PM, Josh Berkus wrote:
> Tom,
>
>> On further reflection, what the "policy" was actually about was not that
>> we should forbid users from creating potentially-confusing aggregates
>> themselves, but only that we'd avoid having any *built in* aggregates with
>> this hazard. So maybe I'm overthinking this, and the correct reading is
>> just that we should have a policy against built-in variadic aggregates.
> Yes. I think we can assume that anyone smart enough to create a
> variadic aggregate is smart enough to put ORDER BY in the right place.
>
>

It's not the creator who is in danger, though, it's the user of the
aggregate function, AIUI. So unless you're saying that anyone smart
enough to use a variadic aggregate can be assumed to be smart enough to
put ORDER BY in the right place, I don't think this argument holds.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-08-29 23:10:15 Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Previous Message Stephen Frost 2013-08-29 22:42:13 Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])