On 11/14/2012 02:37 PM, Tom Lane wrote:

What I'm imagining is a very very simple addition to COPY that just
allows it to execute popen() instead of fopen() to read or write the
data source/sink.  What you suggest would require hundreds of lines and
create many opportunities for new bugs.

                        

That's certainly a better answer than any I've had. I accept the reasoning.

cheers

andrew



--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to