Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
From: "Etsuro Fujita" <fujita.etsuro@lab.ntt.co.jp>
To: "'Andrew Dunstan'" <andrew@dunslane.net>, "'Dimitri Fontaine'" <dimitri@2ndQuadrant.fr>
Cc: "'Tom Lane'" <tgl@sss.pgh.pa.us>, <pgsql-hackers@postgresql.org>, "'Alvaro Herrera'" <alvherre@2ndquadrant.com>, "'Pavel Stehule'" <pavel.stehule@gmail.com>
Date: 2012-09-14T07:48:50Z
Lists: 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 >