| From: | David Rysdam <drysdam(at)ll(dot)mit(dot)edu> |
|---|---|
| To: | |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: COPY not handling BLOBs |
| Date: | 2004-08-04 17:58:58 |
| Message-ID: | 411123E2.2060205@ll.mit.edu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Doug McNaught wrote:
>David Rysdam <drysdam(at)ll(dot)mit(dot)edu> writes:
>
>
>
>>Right now I'm having to write a program to create all the large
>>objects up front and record the OIDs in a file which I will then COPY
>>in with the rest of my data.
>>
>>
>
>You might consider using "bytea" instead of large objects, unless you
>need the lo_read()/lo_seek() API in your client app... I'm not
>super-familiar with how bytea and COPY work together, though.
>
>-Doug
>
>
bytea will only go up to "several thousand bytes" according to the
docs. I assume it's not very precise because the maximum is 8196 -
$other_fields_in_row. My binary data could be a couple times that or
even much bigger for other apps.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Elphick | 2004-08-04 18:02:24 | Re: altering the datatype of a column. |
| Previous Message | Tom Lane | 2004-08-04 17:57:12 | Re: Casting timestamp with time zone to varchar automatically |