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

From Pavel Stehule
Subject Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Date
Msg-id CAFj8pRCXfKX8z-8o6LWjOdzq8b=KWABEfD+fn7S95BEbadPw4w@mail.gmail.com
Whole thread Raw
In response to Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
2012/9/13 Alvaro Herrera <alvherre@2ndquadrant.com>:
> Excerpts from Etsuro Fujita's message of jue sep 13 06:13:26 -0300 2012:
>> I'd like to add the following options to the SQL COPY command and the psql \copy
>> instruction:
>>
>>     * PREPROCESSOR: Specifies the user-supplied program for COPY IN.  The data
>> from an input file is preprocessed by the program before the data is loaded into
>> a postgres table.
>>     * POSTPROCESSOR: Specifies the user-supplied program for COPY OUT.  The data
>> from a postgres table is postprocessed by the program before the data is stored
>> in an output file.
>
> External programs?  I don't like the sound of that; there all kinds of
> open questions, security concerns, and process management problems.
> What if the pre- and postprocessors were functions instead?

+1

this can be solved via pipe and outer processes

Pavel

>
> --
> Álvaro Herrera                http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Next
From: Simon Riggs
Date:
Subject: Re: remove dead ports?