| From: | Matthew Wakeling <matthew(at)flymine(dot)org> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Eliot Gable <egable+pgsql-performance(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Function Language Performance: C vs PL/PGSQL |
| Date: | 2010-06-01 12:59:35 |
| Message-ID: | alpine.DEB.2.00.1006011359030.4083@aragorn.flymine.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, 1 Jun 2010, Stephen Frost wrote:
> * Matthew Wakeling (matthew(at)flymine(dot)org) wrote:
>> The major case I found when writing pl/pgsql was when trying to build
>> arrays row by row. AFAIK when I tried it, adding a row to an array caused
>> the whole array to be copied, which put a bit of a damper on performance.
>
> Using the built-ins now available in 8.4 (array_agg), that copying
> doesn't happen any more.
Thanks. I had wondered if that had been improved.
Matthew
--
Our riverbanks and seashores have a beauty all can share, provided
there's at least one boot, three treadless tyres, a half-eaten pork
pie, some oil drums, an old felt hat, a lorry-load of tar blocks,
and a broken bedstead there. -- Flanders and Swann
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brad Nicholson | 2010-06-01 13:17:31 | Re: Zeus IOPS |
| Previous Message | Stephen Frost | 2010-06-01 12:54:53 | Re: PostgreSQL Function Language Performance: C vs PL/PGSQL |