Re: Let file_fdw access COPY FROM PROGRAM

From: Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(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-07 03:44:19
Message-ID: CAMsr+YF4fjJXgA-fGjTQyjc6dAam195djKhaVnbwV+8AFmEvKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7 September 2016 at 11:37, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:
> On Tue, Sep 6, 2016 at 11:24 PM, Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>
> wrote:
>>
>> On 7 September 2016 at 11:21, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
>> wrote:
>> > On Tue, Sep 6, 2016 at 6:53 PM, Craig Ringer
>> > <craig(dot)ringer(at)2ndquadrant(dot)com>
>>
>> > And the TAP test would detect the operating system and know to create an
>> > FDW
>> > that has the PROGRAM value 'cat test_data.csv' on Unix, 'type
>> > test_data.csv'
>> > on windows, and 'type test_data.csv;1' on VMS?
>>
>> Right. Or just "perl emit_test_data.pl" that works for all of them,
>> since TAP is perl so you can safely assume you have Perl.
>
>
> Thanks. I was mentally locked in more basic OS commands. Am I right in
> thinking perl is about the *only* OS command you can be sure is on every
> architecture?

Probably, there's a lot of crazy out there.

TAP tests can be conditionally run based on architecture, but
something like this is probably worth testing as widely as possible.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-09-07 03:57:51 Re: [PATCH] COPY vs \copy HINT
Previous Message Corey Huinker 2016-09-07 03:37:55 Re: Let file_fdw access COPY FROM PROGRAM