DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=CnK6hALvWf5nIQjtyxe85LjY11HdMhy3rzhtLIfNYUQ/SuJQ1UQQ3KAaPkhqz7rR6IwgGCJPt1KIpgIkM79Jyc/eeCr7Gqvpidghtnm7K5Xf5AqdY/RCGSspFzQc+7xj1Oe6fBEnje1IAbZwf3UBSfRTllwTLM7dz9XlXKUZ6So=
Message-ID: <523e84030612231908s32ef5145s4e18582b4a579d07@mail.gmail.com>
Date: Sat, 23 Dec 2006 19:08:24 -0800
From: Mason <freemason@gmail.com>
To: pgsql-sql@postgresql.org
Subject: I would like to alter the COPY command
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

What I have is data with two different characters for "start quote"
and "end quote".  In my case it's '[' and ']', but it could be
anything from "smart quotes", to parentheses, to brackets, braces, ^/$
in regexps, etc.  I think this isn't too unreasonable a feature to
have to make copy more functional when importing data that is
difficult to transform properly beforehand (in my case is about half a
terabyte of log files, which takes hours and hours, just to cat, let
alone reparse and dump into COPY).

Now, in my case I can just say "cat file | tr '[]' '""' | psql -f
import.sql", but then I lose the ability for psql to do anything smart
like using mmap (I'm making assumptions that it does anything smart
like that, but even if it doesn't now, it could some day).

So, I'm a passable c/c++ programmer, when I have to be, so
theoretically I can do the work myself, but I have never touched
postgres before, so I don't know where to begin.  Any ideas how to add
this?