Re: exposing COPY API - Mailing list pgsql-hackers

From Robert Haas
Subject Re: exposing COPY API
Date
Msg-id AANLkTin0__cXY-uqjLQuFauuSuEZxGV7UC1EzGPTzWjw@mail.gmail.com
Whole thread Raw
In response to Re: exposing COPY API  (Shigeru HANADA <hanada@metrosystems.co.jp>)
Responses Re: exposing COPY API
List pgsql-hackers
On Tue, Feb 8, 2011 at 4:42 AM, Shigeru HANADA
<hanada@metrosystems.co.jp> wrote:
> On Tue, 8 Feb 2011 17:49:09 +0900
> Itagaki Takahiro <itagaki.takahiro@gmail.com> wrote:
>
>> On Tue, Feb 8, 2011 at 09:38, Andrew Dunstan <andrew@dunslane.net> wrote:
>> > Here is a patch against the latest revision of file_fdw to exercise this
>> > API. It includes some regression tests, and I think apart from one or two
>> > small details plus a requirement for documentation, is complete.
>>
>> The patch contains a few fixes for typo in the original patch.
>> Hanada-san, could you take them into the core file_fdw patch?
>
> Thanks, I've applied to my local repo.
>
> s/Centinel/Sentinel/
> s/Vaidate/Validate/
> s/reaind/reading/
>
> Recent file_fdw is available here:
> http://git.postgresql.org/gitweb?p=users/hanada/postgres.git;a=summary
>
> I'll submit revised file_fdw patch after removing IsForeignTable()
> catalog lookup along Heikki's proposal.

So I'm a bit confused.  I don't see the actual copy API change patch
anywhere here.  Are we close to getting something committed there?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [pgsql-general 2011-1-21:] Are there any projects interested in object functionality? (+ rule bases)
Next
From: Simon Riggs
Date:
Subject: Re: Named restore points