| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY |
| Date: | 2012-11-14 16:56:57 |
| Message-ID: | 21137.1352912217@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 11/14/2012 11:39 AM, Tom Lane wrote:
>> What happened to the previous proposal of treating the COPY
>> target as a pipe specification, ie
> I'd like to be able to filter STDIN if possible - with this syntax how
> is COPY going to know to hook up STDIN to the program?
Huh? That's fairly nonsensical for the backend-side case; there's no
way that stdin (or stdout) of a backend is going to connect anywhere
useful for this purpose. As for doing it on the psql side (\copy),
I think it would be more or less automatic. If you do say
foo | psql -c "\copy tab from 'bar |'" dbname
then bar is going to inherit psql's stdin, which is coming from foo.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-11-14 17:18:19 | Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY |
| Previous Message | Andrew Dunstan | 2012-11-14 16:50:56 | Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY |