Horton

Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION

Daniel Farina <drfarina@gmail.com>

View thread View on postgr.es
From: Daniel Farina <drfarina@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Jeff Davis <pgsql@j-davis.com>, Pavel Stehule <pavel.stehule@gmail.com>, Hannu Krosing <hannu@krosing.net>, Greg Smith <greg@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Daniel Farina <dfarina@truviso.com>, pgsql-hackers@postgresql.org
Date: 2009-11-26T05:49:17Z
Lists: pgsql-hackers 
On Wed, Nov 25, 2009 at 9:35 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> On Wed, November 25, 2009 3:56 pm, Jeff Davis wrote:
>>
>> I worry that we're getting further away from the original problem. Let's
>> allow functions to get the bytes of data from a COPY, like the original
>> proposal. I am not sure COPY is the best mechanism to move records
>> around when INSERT ... SELECT already does that.
>>
>
>
> I am not at all sure I think that's a good idea, though. We have
> pg_read_file() for getting raw bytes from files. Building that into COPY
> does not strike me as a good fit.

I think we speak of the opposite direction...

fdr