| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SQL/MED - file_fdw |
| Date: | 2010-12-13 16:25:09 |
| Message-ID: | 4D0648E5.9050400@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/13/2010 11:12 AM, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)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.
>
In that case I guess I'll need to do what Shigeru-san has done, and copy
large parts of copy.c.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hitoshi Harada | 2010-12-13 16:25:28 | Re: SQL/MED - core functionality |
| Previous Message | Florian Pflug | 2010-12-13 16:21:49 | Re: Problem with pg_upgrade (8.4 -> 9.0) due to ALTER DATABASE SET ROLE |