| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Johnston <polobo(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Function Column Expansion Causes Inserts To Fail |
| Date: | 2011-05-31 22:15:10 |
| Message-ID: | BANLkTimkDy9vLPOzPY13_fdJme2YYSVugg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, May 31, 2011 at 5:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
>> I've never taken the time to really get my head around 'lateral'
>> enough to say for sure if it provides clean workarounds for all the
>> cases that get people into hot water. The case that used to get me a
>> lot is (the unfortunately generally under utilized) custom aggregates.
>
>> problem:
>> select bar_id, (some_agg(foo)).* from foo join bar ... group by bar_id;
>
> Hm, really? I'd expect that nodeAgg's attempts to collect identical
> aggregate calls into one would keep you out of trouble there. That
> hack unfortunately doesn't generalize to ordinary functions ...
you appear to be right -- memory failing here.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2011-06-01 00:08:13 | Re: UTC4115FATAL: the database system is in recovery mode |
| Previous Message | Tom Lane | 2011-05-31 22:01:19 | Re: Function Column Expansion Causes Inserts To Fail |