Re: pg_upgrade project status

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: jd(at)commandprompt(dot)com
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade project status
Date: 2009-01-27 15:56:33
Message-ID: 497F2EB1.7040202@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:
> On Tue, 2009-01-27 at 09:48 -0500, Andrew Dunstan wrote:
>
>
>>> We don't require perl for any other feature, do we? Seems like a
>>> pretty onerous requireemnt for Windows in particular. We do use perl
>>> in the build scripts, but that's only required if you want to compile
>>> from source.
>>>
>> Well, from that POV the only portable thing is to translate it into C.
>> That's just a whole lot more work (remember initdb?). The perl port for
>> Windows is easily installable, widely used and well regarded. It doesn't
>> strike me as too high a price to pay for the ability to do upgrades, but
>> I'll defer to more Windows-centric commenters.
>>
>
> Actually as much as perl is ubiquitous it isn't. What version of perl
> shall we require? Will we require other modules? Does that version work
> on all our supported platforms (HPUX, NETBSD?)
>
>
>

That's what my brief examination of the script was about - looking to
see if it could be translated portably. I think it very probably can. I
suspect it won't need any modules at all. I suspect any

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-01-27 15:57:18 Re: More FOR UPDATE/FOR SHARE problems
Previous Message Joshua D. Drake 2009-01-27 15:52:10 Re: pg_upgrade project status