| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: psql \setfileref |
| Date: | 2016-10-09 17:14:48 |
| Message-ID: | CADkLM=e=DtYm70T+hQznzfYSowwA39DmccHdefJKgUoNeWU-hA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Oct 9, 2016 at 12:12 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:
>
>
> 2016-10-09 17:27 GMT+02:00 Corey Huinker <corey(dot)huinker(at)gmail(dot)com>:
>
>> here is new update - some mentioned issues are fixed + regress tests and
>>>> docs
>>>>
>>>
>>>
>>>
>> This 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-10-09 17:21:12 | Re: proposal: psql \setfileref |
| Previous Message | Andrew Dunstan | 2016-10-09 16:53:34 | cygwin64 assertion failure |