Re: pg_upgrade test mods for Windows/Mingw

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade test mods for Windows/Mingw
Date: 2012-09-03 13:16:45
Message-ID: 5044ADBD.4040509@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 09/02/2012 11:53 PM, Gurjeet Singh wrote:
> On Sun, Sep 2, 2012 at 11:29 PM, Andrew Dunstan <andrew(at)dunslane(dot)net
> <mailto:andrew(at)dunslane(dot)net>> wrote:
>
> The attached patch is what I had to do to get pg_upgrade's "make
> check" to run on Windows under Mingw. Mostly the changes have to
> do with getting paths right between Windows and MSys, or calling
> generated .bat files instead of shell scripts.
>
>
> When reading shell script code like this
>
> `uname -a | sed 's/.* //'` = Msys
>
> and
>
> sed -i -e 's,/,\\,g' -e 's,\\s\\q ,/s/q ,' delete_old_cluster.bat
> 2>/dev/null
>
> I find it easier to understand and maintain if the comments also
> describe what is the original string format that this
> pattern-matching expects, like:
>
> # We expect `uname -a` output like:
> # Windows_NT4.0 Msys
>
> and
>
> # We expect lines of the format:
> # abc/xyz/def/
> # and we convert them to
> # abc\xyz\def
>
>
> BTW, would `uname -o` eliminate the need of pattern matching in the
> first snippet? The Wikipedia [1] article suggests so.
>
> [1] http://en.wikipedia.org/wiki/Uname
>
>

Yeah it would. This wasn't intended as a final patch anyway, just as
notice of what I actually had working in case anyone else wanted to try.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-09-03 13:48:01 Re: 9.2: Describing a security barrier view in psql
Previous Message Alvaro Herrera 2012-09-03 13:15:06 Re: [bugfix] sepgsql didn't follow the latest core API changes