| From: | Dani Oderbolz <oderbolz(at)ecologic(dot)de> |
|---|---|
| To: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: an aggregate array function |
| Date: | 2003-07-29 15:23:22 |
| Message-ID: | 3F26916A.7030508@ecologic.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure wrote:
> Dear hackers,
>
>
>
> Do you think there would be any use for an aggregate which returns an
> array of the aggregated (usually simple) type? Has this already been
> done by anyone? I looked at the source and noticed that for each
> inserted item, the array utility functions perform a deep copy of the
> entire array (plus a reallocation). Normally, this is no big deal,
> but if executed in the query stage, it could be kind of slow. I also
> noticed that null values inside is an item on the todo list. Is
> anybody currently working on this?
>
>
>
> Merlin
>
I got another question to this:
why does PostgreSQL support Arrays in the first place?
For my taste, its a very messy concept...
Regards,
Dani
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Gearon | 2003-07-29 15:30:00 | Re: concurrent writes |
| Previous Message | Andrew Dunstan | 2003-07-29 15:08:42 | Re: Make clean fails |