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

From Etsuro Fujita
Subject Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Date
Msg-id 001601cd962c$d4e81780$7eb84680$@lab.ntt.co.jp
Whole thread Raw
In response to Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY  ("Etsuro Fujita" <fujita.etsuro@lab.ntt.co.jp>)
List pgsql-hackers
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]

> I wrote:
> > "Etsuro Fujita" <fujita.etsuro@lab.ntt.co.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.

OK  I'll revise the patch.

Thank you for your advice!

Best regards,
Etsuro Fujita




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Next
From: Bruce Momjian
Date:
Subject: Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed