Horton

Re: exposing COPY API

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Shigeru HANADA <hanada@metrosystems.co.jp>
Cc: Itagaki Takahiro <itagaki.takahiro@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-02-09T17:26:47Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Allow the low level COPY routines to read arbitrary numbers of fields.

On Wed, Feb 9, 2011 at 7:38 AM, Shigeru HANADA
<hanada@metrosystems.co.jp> wrote:
> On Tue, 8 Feb 2011 08:49:36 -0500
> Robert Haas <robertmhaas@gmail.com> wrote:
>> On Tue, Feb 8, 2011 at 4:42 AM, Shigeru HANADA
>> <hanada@metrosystems.co.jp> wrote:
>> > 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?
>
> I'm sorry but I might have missed your point...
>
> I replied here to answer to Itagaki-san's mention about typos in
> file_fdw patch.
>
> Or, would you mean that file_fdw should not depend on "copy API change"
> patch?

I mean that this thread is entitled "exposing copy API", and I'm
wondering when and if the patch to expose the COPY API is going to be
committed.

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