From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Etsuro Fujita" <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | "'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-09-19 03:38:33 |
Message-ID: | 12731.1348025913@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> "Etsuro Fujita" <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> writes:
>> I have a question. I think it would be also better to extend the syntax for the
>> SQL COPY command in the same way, ie,
>> COPY foo from '/home/pgsql/decompress.sh /home/pgsql/foo.csv.gz |' with format
>> 'csv'
> Yeah, sure --- that case is already superuser-only, so why not give it
> the option of being a popen instead of just fopen.
BTW, one thought that comes to mind is that such an operation is
extremely likely to fail under environments such as SELinux. That's
not necessarily a reason not to do it, but we should be wary of
promising that it will work everywhere. Probably a documentation note
about this would be enough.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gibheer | 2012-09-19 04:09:51 | Re: 9.2 Cascading replication after slave promotion |
Previous Message | Tom Lane | 2012-09-19 03:32:48 | Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY |