Re: Let file_fdw access COPY FROM PROGRAM - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: Let file_fdw access COPY FROM PROGRAM
Date
Msg-id CADkLM=eoQpzc+eHQUwnPxg4XY30EBLSYutHiPb7vj=5hOtcybg@mail.gmail.com
Whole thread
In response to Re: Let file_fdw access COPY FROM PROGRAM  (Craig Ringer <craig.ringer@2ndquadrant.com>)
List pgsql-hackers
On Thu, Sep 8, 2016 at 6:59 PM, Craig Ringer <craig.ringer@2ndquadrant.com> wrote:

On 9 Sep. 2016 03:45, "Corey Huinker" <corey.huinker@gmail.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".

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Let file_fdw access COPY FROM PROGRAM
Next
From: Jeff Janes
Date:
Subject: Re: High-CPU consumption on information_schema (only) query