Postgres Pro
Downloads
Home   >   mailing lists

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

From Craig Ringer
Subject Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Date
Msg-id 50581D99.3030101@ringerc.id.au
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
Tree view 
On 09/13/2012 10:25 PM, Tom Lane wrote:
> I think it would be a lot better if this were designed so that the
> processor programs executed on client side.  Which would probably make
> it not a COPY patch at all, but something in psql.

Either that, or allow the pre- and post- processors to be programs 
written in a (possibly trusted) PL.

I can't say I really see the point though, when it's easy to just filter 
the csv through a pipeline.

--
Craig Ringer

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: _FORTIFY_SOURCE by default?
Next
From: Florian.Schoppmann@emc.com (Florian Schoppmann)
Date:
Subject: Invalid optimization of VOLATILE function in WHERE clause?