Re: Let file_fdw access COPY FROM PROGRAM

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Subject: Re: Let file_fdw access COPY FROM PROGRAM
Date: 2016-09-08 23:06:59
Message-ID: CADkLM=eoQpzc+eHQUwnPxg4XY30EBLSYutHiPb7vj=5hOtcybg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 8, 2016 at 6:59 PM, Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>
wrote:

> On 9 Sep. 2016 03:45, "Corey Huinker" <corey(dot)huinker(at)gmail(dot)com> wrote:
> >
> >
>
> > Stylistically, would a separate .pl file for the emitter be preferable
> to something inline like
> >
> >> perl -e 'print "a\tb\tcc\t4\n"; print "b\tc\tdd\t5\n"'
>
> I'd be fine with that and a suitable comment. Just be careful with
> different platforms' shell escaping rules.
>
Do perl command switches on windows/VMS use /e instead of -e? If so,
that'd be a great argument doing just "perl filename".

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2016-09-08 23:36:59 Re: High-CPU consumption on information_schema (only) query
Previous Message Craig Ringer 2016-09-08 22:59:32 Re: Let file_fdw access COPY FROM PROGRAM