| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> |
| Cc: | Madhu Ramachandran <iammadhu(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: copy command and blobs |
| Date: | 2011-01-20 21:11:33 |
| Message-ID: | 21060.1295557893@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> writes:
> Madhu Ramachandran wrote:
>> i have a table with OID column.. I want to use the copy command to
>> insert bunch of rows (1 million).
>> but iam unable to specify the correct format for the oid type (i have
>> .jpg files to be stored in this column)..
> Huh? oid is a keyword, an automatically generated row id, and is
> deprecated. You shouldn't be doing anything with it, much less copying it.
I think what the OP actually means is he's thinking of importing some
images as large objects, then storing their OIDs in a user (not system)
column of type oid. COPY can't be used for that though.
It might be better to use a bytea column, if you're willing to deal with
bytea's weird escaping rules.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-01-21 17:09:12 | Re: "NOT IN" substantially slower in 9.0.2 than 8.3.13 - NOT EXISTS runs fast in both 8.3.13 and 9.0.2 |
| Previous Message | Mladen Gogala | 2011-01-20 20:17:24 | Re: copy command and blobs |