Re: BUG #3852: Could not create complex aggregate

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Sokolov Yura <funny(dot)falcon(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: BUG #3852: Could not create complex aggregate
Date: 2008-01-11 18:43:43
Message-ID: 23148.1200077023@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> Tom Lane wrote:
>> I think we could make enforce_generic_type_consistency() clearer by
>> adding an additional argument "bool allow_poly" which specifies
>> whether polymorphic "actual" argument and result types are allowed.

> This sounds like a reasonable plan to me.

>> Although this problem really goes quite far back, I think it's probably
>> not interesting to back-patch further than 8.2, because AFAICS the
>> interesting cases involve aggregates with more than one argument.

> I agree, especially since this is the first time anyone has complained.

I've applied a patch along these lines, although I desisted from
back-patching it. It seems a bit like a new feature, and also I'm not
100% sure we have all the bases covered even yet.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-01-11 19:56:08 Re: [SQL] (possible) bug with constraint exclusion
Previous Message Magnus Hagander 2008-01-11 14:47:00 Re: BUG #3868: Unattended install fails

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2008-01-11 18:48:25 proposed libpq type system changes 0.9
Previous Message Simon Riggs 2008-01-11 17:31:30 Re: Dynamic Partitioning using Segment Visibility Maps