| From: | Ryan Kelly <rpkelly22(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Jim Nasby <jim(at)nasby(dot)net>, "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Karol Trzcionka <karlikt(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: RETURNING syntax for COPY |
| Date: | 2013-05-08 19:44:40 |
| Message-ID: | 20130508194440.GC9650@llserver.lakeliving.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 05/08/13, 2013 at 03:38:10PM -0400, Andrew Dunstan wrote:
>
> On 05/08/2013 03:23 PM, Jim Nasby wrote:
> >>WITH new_data AS (
> >> COPY FROM ...
> >> RETURNING id, field_to_check
> >>)
> >
>
> Why is this better than this, which you can do today?
>
> WITH new_data AS (
> INSERT into ... FROM foreign_table_with_file_fdw RETURNING ...
> )
>
>
> The whole reason I abandoned trying to do this sort of thing with
> COPY was that I realized the FDW would provide what I wanted.
You need to first CREATE EXTENSION file_fdw. Then you need to CREATE
SERVER. Then CREATE FOREIGN TABLE. Which requires appropriate permission
to do those things, and certainly has no hope of working on the client
side.
-Ryan P. Kelly
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2013-05-08 19:48:48 | Re: GSOC Student Project Idea |
| Previous Message | Andrew Dunstan | 2013-05-08 19:38:10 | Re: RETURNING syntax for COPY |