| From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
| Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Michael Glaesemann" <grzm(at)seespotcode(dot)net>, Decibel! <decibel(at)decibel(dot)org>, "Jeremy Drake" <pgsql(at)jdrake(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions] |
| Date: | 2007-08-15 04:50:44 |
| Message-ID: | 162867790708142150m6353f598md7aa0f9988554bee@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2007/8/15, Merlin Moncure <mmoncure(at)gmail(dot)com>:
> On 8/14/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > TODO item?
>
> I would say yes...array_accum is virtually an essential function when
> working with arrays and the suggested array_to_set (and it's built in
> cousin, _pg_expand_array) really should not be built around
> generate_series when a C function is faster and will scale much
> better.
>
Hello Merlin
array_accum is good sample of PostgreSQL possibilities. But it is slow.
SELECT ARRAY(SELECT ... FROM ...)) is much faster. :(
so I unlike not necessary aggregate functions
I agree. These constructs can be showed in doc
Regards
Pavel Stehule
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2007-08-15 05:06:43 | Re: CVS corruption/mistagging? |
| Previous Message | Pavel Stehule | 2007-08-15 04:47:05 | Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions] |