Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY

From: "Etsuro Fujita" <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: "'Andrew Dunstan'" <andrew(at)dunslane(dot)net>, "'Dimitri Fontaine'" <dimitri(at)2ndQuadrant(dot)fr>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, "'Alvaro Herrera'" <alvherre(at)2ndquadrant(dot)com>, "'Pavel Stehule'" <pavel(dot)stehule(at)gmail(dot)com>
Subject: Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Date: 2012-09-14 07:48:50
Message-ID: 001801cd924d$6115fb20$2341f160$@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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(at)dunslane(dot)net]
> Sent: Friday, September 14, 2012 2:27 AM
> To: Dimitri Fontaine
> Cc: Tom Lane; Etsuro Fujita; pgsql-hackers(at)postgresql(dot)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(at)sss(dot)pgh(dot)pa(dot)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
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2012-09-14 08:25:08 Reduce palloc's in numeric operations.
Previous Message Kyotaro HORIGUCHI 2012-09-14 07:26:04 Re: Identity projection