Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY - Mailing list pgsql-hackers

From Tom Lane
Subject Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Date
Msg-id 21137.1352912217@sss.pgh.pa.us
Whole thread Raw
In response to Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Next
From: Andrew Dunstan
Date:
Subject: Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY