Re: exposing COPY API - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: exposing COPY API
Date
Msg-id AANLkTin-KbNPz+h8sRGsNOqKmq-4DnccM6G8-HjybLto@mail.gmail.com
Whole thread Raw
In response to Re: exposing COPY API  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: exposing COPY API  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Fri, Feb 4, 2011 at 11:32, Andrew Dunstan <andrew@dunslane.net> wrote:
> Umm, where? I can't find this in the documentation
> <http://pgbulkload.projects.postgresql.org/pg_bulkload.html>

Here:
http://pgbulkload.projects.postgresql.org/pg_bulkload.html#filter

> The object, as I have explained previously, is to have a FDW that returns a
> text array from a (possibly irregularly shaped) file.

I remember the text array proposal, but if the extension is written in C,
it can only handle one kind of input files. If another file is broken
in a different way, you need to rewrite the C code, no?

-- 
Itagaki Takahiro


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: keeping a timestamp of the last stats reset (for a db, table and function)
Next
From: Andrew Dunstan
Date:
Subject: Re: exposing COPY API