| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, 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-10 04:07:08 |
| Message-ID: | CAFj8pRBs46ciKapeq4ES0Q4Yk9xA9X2yEX6kB1RqSkCFmGOWQQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2016-10-10 5:26 GMT+02:00 Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>:
> On 10/9/16 9:54 PM, Bruce Momjian wrote:
>
>> 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.
>>>
>> And it would need to be \:file_ref in COPY so real data doesn't trigger
>> it.
>>
>
> ISTM it'd be much saner to just restrict file ref's to only working with
> psql's \COPY, and not server-side COPY.
>
What should be a benefit, use case for file ref for client side \COPY ?
Regards
Pavel
> --
> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
> Experts in Analytics, Data Architecture and PostgreSQL
> Data in Trouble? Get it in Treble! http://BlueTreble.com
> 855-TREBLE2 (855-873-2532) mobile: 512-569-9461
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2016-10-10 04:51:07 | Remove vacuum_defer_cleanup_age |
| Previous Message | Corey Huinker | 2016-10-10 04:04:09 | Re: proposal: psql \setfileref |