| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Jeff Davis" <pgsql(at)j-davis(dot)com> |
| Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Daniel Farina" <drfarina(at)gmail(dot)com>, "Hannu Krosing" <hannu(at)krosing(dot)net>, "Greg Smith" <greg(at)2ndquadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Daniel Farina" <dfarina(at)truviso(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |
| Date: | 2009-11-26 05:35:42 |
| Message-ID: | 51560.76.125.11.227.1259213742.squirrel@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2009-11-26 05:49:17 | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |
| Previous Message | Florian G. Pflug | 2009-11-26 04:36:28 | Re: ALTER TABLE, find_composite_type_dependencies and locking (Confirmed) |