Prev: Drop one-argument string_agg? (was Re: [BUGS] string_aggdelimiter having no effect with order by)
Next: [HACKERS] PL/pgSQL EXECUTE '..' USING with unknown
From: Tom Lane on 5 Aug 2010 15:50
Josh Berkus <josh(a)agliodbs.com> writes:
> On 8/5/10 12:18 PM, Robert Haas wrote:
>> Could we arrange to emit this error message only when there is an
>> aggregate with the same name but different arguments?

> Personally, I don't see this as really necessary. Just mentioning ORDER
> BY in the hint will be enough to give people the right place to look.

I suppose Robert is more concerned about the possibility that we emit
the ORDER BY hint when that isn't really the source of the problem.
But after all, the reason it's a hint and not the primary error message
is that it's not certain to be helpful.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: Drop one-argument string_agg? (was Re: [BUGS] string_aggdelimiter having no effect with order by)
Next: [HACKERS] PL/pgSQL EXECUTE '..' USING with unknown