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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Date: 2012-11-14 20:15:38
Message-ID: 50A3FBEA.7010506@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 11/14/2012 02:37 PM, Tom Lane wrote:

> What I'm imagining is a very very simple addition to COPY that just
> allows it to execute popen() instead of fopen() to read or write the
> data source/sink. What you suggest would require hundreds of lines and
> create many opportunities for new bugs.
>
>

That's certainly a better answer than any I've had. I accept the reasoning.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-11-14 20:21:29 Re: Enabling Checksums
Previous Message Tom Lane 2012-11-14 20:06:00 Re: Enabling Checksums