Re: proposal: psql \setfileref
| От | Corey Huinker |
|---|---|
| Тема | Re: proposal: psql \setfileref |
| Дата | |
| Msg-id | CADkLM=e=DtYm70T+hQznzfYSowwA39DmccHdefJKgUoNeWU-hA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: proposal: psql \setfileref (Pavel Stehule <pavel.stehule@gmail.com>) |
| Ответы |
Re: proposal: psql \setfileref
|
| Список | pgsql-hackers |
On Sun, Oct 9, 2016 at 12:12 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
2016-10-09 17:27 GMT+02:00 Corey Huinker <corey.huinker@gmail.com>:here is new update - some mentioned issues are fixed + regress tests and docsThis might tie into some work I'm doing. Is there any way these filerefs could be used as the inline portion of a COPY command?i.e. like this:COPY my_table FROM STDIN:file_ref
\.I understand, but I am not sure how difficult implementation it is. This part (COPY input) doesn't support parametrization - and parametrization can have a negative performance impact.Regards
I may not understand your response. I was thinking we'd want :file_ref to simply 'cat' the file (or program) in place. The fact that the output was consumed by COPY was coincidental. Does that chance your response?
В списке pgsql-hackers по дате отправления: