Re: exposing COPY API

From: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: exposing COPY API
Date: 2011-02-04 02:43:40
Message-ID: AANLkTin-KbNPz+h8sRGsNOqKmq-4DnccM6G8-HjybLto@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 4, 2011 at 11:32, Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Conor Walsh 2011-02-04 02:45:09 Re: [HACKERS] Slow count(*) again...
Previous Message Greg Smith 2011-02-04 02:37:54 Re: keeping a timestamp of the last stats reset (for a db, table and function)