| From: | Barry Lind <blind(at)xythos(dot)com> |
|---|---|
| To: | Chris Smith <chris(at)mindiq(dot)com> |
| Cc: | Jeremiah Jahn <jeremiah(at)goodinassociates(dot)com>, postgres jdbc <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: create BLOB question |
| Date: | 2003-02-12 21:19:51 |
| Message-ID: | 3E4ABA77.2060407@xythos.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Chris,
I beleive it is both; client and server will both have copies in memory
of the entire bytea value.
--Barry
Chris Smith wrote:
> Barry Lind quoted:
>
>>The bytea data type is not well suited
>>for storing very large amounts of binary data. While a column of type
>>bytea can hold up to 1 GB of binary data, it would require a huge amount
>>of memory (RAM) to process such a large value.
>
>
> Is this referring to the JDBC driver, or the database back end? I have
> implemented a fix for this in the JDBC driver, but was wondering if the back
> end is going to be okay with it... anyone know if the entire data gets held
> in RAM at once in the database process itself?
>
> --
> www.designacourse.com
> The Easiest Way to Train Anyone... Anywhere.
>
> Chris Smith - Lead Software Developer/Technical Trainer
> MindIQ Corporation
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roger Hand | 2003-02-12 23:27:54 | case problem with moveToInsertRow() |
| Previous Message | Chris Smith | 2003-02-12 20:57:02 | Re: create BLOB question |