Re: COPY not handling BLOBs - Mailing list pgsql-general

From David Rysdam
Subject Re: COPY not handling BLOBs
Date
Msg-id 411123E2.2060205@ll.mit.edu
Whole thread Raw
In response to Re: COPY not handling BLOBs  (Doug McNaught <doug@mcnaught.org>)
Responses Re: COPY not handling BLOBs  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: COPY not handling BLOBs  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-general
Doug McNaught wrote:

>David Rysdam <drysdam@ll.mit.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.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Casting timestamp with time zone to varchar automatically
Next
From: Oliver Elphick
Date:
Subject: Re: altering the datatype of a column.