Re: SQL/MED - file_fdw

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Itagaki Takahiro <itagaki.takahiro@gmail.com>, Shigeru HANADA <hanada@metrosystems.co.jp>, pgsql-hackers@postgresql.org
Date: 2010-12-13T16:12:47Z
Lists: pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Hmm. I don't think that's going to expose enough for what I want to be 
> able to do. I actually had in mind exposing lower level routines like 
> CopyReadAttibutesCSV/CopyReadAttributesText and allowing the Foreign 
> Data Wrapper to manipulate the raw values read (for example from an 
> irregularly shaped CSV file).

I think that exposing the guts of COPY to the open air is a bad idea.
We refactor that code for performance or other reasons every release or
two.  I don't want to find us tied down to the current implementation
because we're afraid of breaking third-party FDWs.

			regards, tom lane