To: Mladen Gogala <mladen.gogala@vmsinfo.com>
cc: Madhu Ramachandran <iammadhu@gmail.com>,
	"pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: copy command and blobs 
In-reply-to: <4D389854.80603@vmsinfo.com> 
References: <AANLkTimGC+t9aADYn2KAXgqTMHwEoBV=Ht3iMV3dnxtZ@mail.gmail.com>
	<4D389854.80603@vmsinfo.com>
Comments: In-reply-to Mladen Gogala <mladen.gogala@vmsinfo.com>
	message dated "Thu, 20 Jan 2011 15:17:24 -0500"
Date: Thu, 20 Jan 2011 16:11:33 -0500
Message-ID: <21060.1295557893@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Mladen Gogala <mladen.gogala@vmsinfo.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