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

From Simon Riggs
Subject Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Date
Msg-id CA+U5nML+qKX=Z=5WXNBs0mKdcNBNPWrmdDZB2hmMWA3oHFULbA@mail.gmail.com
Whole thread Raw
In response to Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY  (Fujii Masao <masao.fujii@gmail.com>)
Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 14 November 2012 15:09, Fujii Masao <masao.fujii@gmail.com> wrote:

>> Here, progname for COPY IN is the user-supplied program that takes filename as
>> its argument and that writes on standard output.
>
> What about further extending the COPY IN syntax to the following?
>
>     COPY table_name FROM 'progname [ option, ... ]' WITH ...
>
> I'd just like to execute
>
>     COPY vmstat_table FROM 'vmstat' WITH ...

I think we should be using FDWs/SRFs here, not inventing new
syntax/architectures for executing external code, so -1 from me.

We can already do
INSERT table SELECT * FROM fdw;
with any logic for generating data lives inside an FDW or SRF.

If we want it in COPY we can have syntax like this...
COPY table FROM (SELECT * FROM fdw)

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Further pg_upgrade analysis for many tables
Next
From: Bruce Momjian
Date:
Subject: Re: Further pg_upgrade analysis for many tables