| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Sergey E(dot) Koposov" <math(at)sai(dot)msu(dot)ru> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: two-argument aggregates and SQL 2003 |
| Date: | 2006-04-13 15:34:14 |
| Message-ID: | 20390.1144942454@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Sergey E. Koposov" <math(at)sai(dot)msu(dot)ru> writes:
> ... Nothing else and nothing internal need not to be changed to
> insert new two-arg. aggregate functions into the core.
> Am I right in this ?
IIRC the main issues are the syntax of CREATE AGGREGATE and the actual
implementation in nodeAgg.c. See previous discussions, eg
http://archives.postgresql.org/pgsql-general/2006-03/msg00512.php
I would really prefer to see CREATE AGGREGATE normalized to have a
syntax comparable to CREATE FUNCTION (or DROP AGGREGATE for that
matter):
CREATE AGGREGATE aggname (typname [, ... ]) ...definition...
but it's not clear how to get there without breaking backwards
compatibility :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-13 15:52:28 | Re: Practical impediment to supporting multiple SSL libraries |
| Previous Message | Stephen Frost | 2006-04-13 15:33:36 | Re: Practical impediment to supporting multiple SSL libraries |