| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | Vidas Makauskas <vms(at)centras(dot)lt>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: outOfMemoryError |
| Date: | 2006-08-30 12:36:07 |
| Message-ID: | A45A5EE0-37AD-47D4-B578-12E3158901B0@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 29-Aug-06, at 8:47 PM, Kris Jurka wrote:
>
>
> On Tue, 29 Aug 2006, Dave Cramer wrote:
>
>> This design is limited by memory.
>>
>> You would be far better off inserting directly instead of using a
>> ResultSet
>
> Actually I think there is a point to be made here. If the
> ResultSet is not scrollable then there is no need to store all the
> inserts that are made to it, so there should be no memory limit.
True, but this is hardly documented. It also suggests adding
complexity for a special case.
>
> Kris Jurka
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-08-30 13:05:42 | Re: Could not determine data type of parameter $1 |
| Previous Message | Markus Schaber | 2006-08-30 11:06:23 | Re: Encoding problem |