| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Artacus <artacus(at)comcast(dot)net> |
| Cc: | Ben <bench(at)silentmedia(dot)com>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: abusing plpgsql array variables |
| Date: | 2008-09-11 12:25:18 |
| Message-ID: | 17414.1221135918@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Artacus <artacus(at)comcast(dot)net> writes:
>> If I want to pass in a text[] argument to a plpgsql function, at what
>> array size am I asking for problems? 100? 10,000? 100,000?
> Yeah, like you I was pretty worried about how it would handle using
> larger arrays. But I was surprised to find that it did a super job of
> handling even large arrays.
Note that this depends quite a lot on what datatype the array elements
are. Fixed-width types like int or float should be fast.
Variable-width types like text or numeric, not so much.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jef Peeraer | 2008-09-11 12:29:45 | Re: xml queries & date format |
| Previous Message | Tom Lane | 2008-09-11 12:20:28 | Re: initdb memory segment creation error |