Re: RETURNING syntax for COPY
От | Tom Lane |
---|---|
Тема | Re: RETURNING syntax for COPY |
Дата | |
Msg-id | 2143.1368033374@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: RETURNING syntax for COPY (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Ответы |
Re: RETURNING syntax for COPY
Re: RETURNING syntax for COPY Re: RETURNING syntax for COPY |
Список | pgsql-hackers |
Heikki Linnakangas <hlinnakangas@vmware.com> writes: > On 08.05.2013 19:44, Tom Lane wrote: >> No there isn't; what you suggest would require FE/BE protocol >> extensions, making it several orders of magnitude more work than the >> other thing. > I'd imagine that the flow would go something like this: > BE FE > CopyInResponse > CopyData > CopyData > ... > CopyDone > RowDescription > DataRow > DataRow > CommandComplete 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. regards, tom lane
В списке pgsql-hackers по дате отправления: