msys2 vs pg_upgrade/test.sh

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: msys2 vs pg_upgrade/test.sh
Date: 2019-09-08 22:06:34
Message-ID: 3227042f-cfcc-745a-57dd-fb8c471f8ddf@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Diagnosing this took quite a lot of time and detective work. For some
reason I don't quite understand, when calling the Windows command
processor in a modern msys2/WindowsServer2019 installation, you need to
double the slash, thus:

    cmd //c foo.bat

Some Internet postings at least seem to suggest this is by design. (FSVO
"design")

I tested this on older versions and the change appears to work, so I
propose to apply the attached patch.

This is the last obstacle I have to declaring msys2 fully supportable.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
pg_upgrade_msys2.patch text/x-patch 760 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2019-09-08 22:14:52 Re: MSVC buildfarm critters are not running modules' TAP tests
Previous Message Tom Lane 2019-09-08 22:00:29 Re: pgsql: Use data directory inode number, not port, to select SysV resour