| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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 17:40:08 |
| Message-ID: | 518A8DF8.4090801@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/08/2013 01:16 PM, Tom Lane wrote:
> That would require the backend to buffer the entire query response,
> which isn't a great idea. I would expect that such an operation would
> need to interleave CopyData to the backend with DataRow responses. Such
> a thing could possibly be built on COPY_BOTH mode, but it would be a lot
> of work (at both ends) for extremely debatable value.
>
> The general idea of COPY is to load data as fast as possible, so weighing
> it down with processing options seems like a pretty dubious idea even if
> the implementation were easy.
>
>
That was my reaction. I would look it this very skeptically.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2013-05-08 17:54:55 | Re: RETURNING syntax for COPY |
| Previous Message | Dimitri Fontaine | 2013-05-08 17:33:50 | Re: RETURNING syntax for COPY |