Re: proposal: psql \setfileref

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: 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 02:54:02
Message-ID: 20161010025402.GB24598@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 9, 2016 at 06:12:16PM +0200, Pavel Stehule 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.

And it would need to be \:file_ref in COPY so real data doesn't trigger
it.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2016-10-10 03:00:34 Re: pg_stat_statements and non default search_path
Previous Message Jim Nasby 2016-10-10 02:51:17 Re: Question / requests.