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 001801cd924d$6115fb20$2341f160$@lab.ntt.co.jp
Whole thread Raw
In response to Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
OK  I will redesign the function.

Thanks everyone for the advice!

Best regards,
Etsuro Fujita

> -----Original Message-----
> From: Andrew Dunstan [mailto:andrew@dunslane.net]
> Sent: Friday, September 14, 2012 2:27 AM
> To: Dimitri Fontaine
> Cc: Tom Lane; Etsuro Fujita; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] WIP patch: add (PRE|POST)PROCESSOR options to COPY
> 
> 
> On 09/13/2012 01:20 PM, Dimitri Fontaine wrote:
> > Tom Lane <tgl@sss.pgh.pa.us> writes:
> >> 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.
> > And pgloader, which already has a part of that feature with the per
> > column reformating facility.
> >
> 
> Yeah, I'd be inclined to say that pre/post processing of this kind is
> really a job for specialized clients.
> 
> cheers
> 
> andrew
> 





pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Identity projection
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Reduce palloc's in numeric operations.