Re: pg_upgrade project status

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 14:52:15
Message-ID: 14145.1233067935@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dave Page <dpage(at)pgadmin(dot)org> writes:
> On Tue, Jan 27, 2009 at 2:39 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
>> I think it's fairly easy to install Perl on Windows actually. It
>> doesn't sound too onerous a requirement if you want in-place upgrade;
>> actually it looks a very reasonable one.

> There are installers for it, but given that we made a point of porting
> everything to C to avoid using any scripting languages on end-user
> machines when we ported to Windows, it seems strange to relax that
> 'policy' now for convenience.

Indeed. We might put up with a perl script for awhile for the sake of
development expediency, but the long-term expectation would have to be
that someone would rewrite it in C. Given that, I wonder whether
there's much point in a rewrite into Perl if we already have a working
shell script. I suppose someone will say "but you'll get no testing
from Windows users then..."

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-01-27 14:54:00 Re: Index Scan cost expression
Previous Message Alvaro Herrera 2009-01-27 14:49:00 Re: pg_upgrade project status