| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Drop one-argument string_agg? (was Re: [BUGS] string_agg delimiter having no effect with order by) |
| Date: | 2010-08-05 19:50:43 |
| Message-ID: | 28696.1281037843@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-05 19:59:31 | Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes |
| Previous Message | Josh Berkus | 2010-08-05 19:27:52 | Re: Drop one-argument string_agg? (was Re: [BUGS] string_agg delimiter having no effect with order by) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-08-05 20:07:01 | Re: Concurrent MERGE |
| Previous Message | Josh Berkus | 2010-08-05 19:45:51 | Re: Concurrent MERGE |