Re: exposing COPY API

From: Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: exposing COPY API
Date: 2011-02-09 12:38:54
Message-ID: 20110209213853.7DFE.6989961C@metrosystems.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 8 Feb 2011 08:49:36 -0500
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Feb 8, 2011 at 4:42 AM, Shigeru HANADA
> <hanada(at)metrosystems(dot)co(dot)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?

Regards,
--
Shigeru Hanada

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-02-09 12:53:20 Re: Sync Rep for 2011CF1
Previous Message Itagaki Takahiro 2011-02-09 12:12:56 Re: Transaction-scope advisory locks