| From: | Fernando Nasser <fnasser(at)redhat(dot)com> |
|---|---|
| To: | Dave Tenny <jeffrey(dot)tenny(at)comcast(dot)net> |
| Cc: | Nicolas Modrzyk <nicolas(dot)modrzyk(at)inrialpes(dot)fr>, Andreas Prohaska <ap(at)apeiron(dot)de>, "'pgsql-jdbc(at)postgresql(dot)org'" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Streaming binary data into db, difference between Blob |
| Date: | 2003-09-10 14:12:24 |
| Message-ID: | 3F5F3148.7040203@redhat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Dave Tenny wrote:
> You could always implement your own logical blob manager that implements
> blob IDs
> and breaks blobs into BYTEA records of a particular (manageable) maximum
> size and associates
> multiple BYTEA chunks with the blob id.
>
> More work, but a least common denominator approach that should be
> portable to other systems as well.
>
However, bytea is _not_ streamed on 7.3 backends (unless the patch is
used, which actually uses postgreSQL Large Objects as a staging area).
That would be fine for 7.4 where bytea values will be streamed though.
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser(at)redhat(dot)com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Tenny | 2003-09-10 14:14:09 | Re: Streaming binary data into db, difference between Blob |
| Previous Message | Fernando Nasser | 2003-09-10 14:05:07 | Re: Streaming binary data into db, difference between Blob |