| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Pavel Stehule <pavel(dot)stehule(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:04:09 |
| Message-ID: | CADkLM=d_xkQR41iknRLUXbNg=bC4GD6v-EYzzPr0sf3-7pjuig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Oct 9, 2016 at 11:26 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> 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.
Which is a great discussion for the thread on "COPY as a set returning
function". I didn't mean to hijack this thread with a misguided tie-in.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-10-10 04:07:08 | Re: proposal: psql \setfileref |
| Previous Message | Corey Huinker | 2016-10-10 04:02:12 | Re: Fast AT ADD COLUMN with DEFAULTs |