Re: pg_upgrade del/rmdir path fix - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_upgrade del/rmdir path fix
Date
Msg-id 20120904144936.GP24132@momjian.us
Whole thread Raw
In response to Re: pg_upgrade del/rmdir path fix  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: pg_upgrade del/rmdir path fix  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_upgrade del/rmdir path fix  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Tue, Sep  4, 2012 at 11:42:58AM -0300, Alvaro Herrera wrote:
> Excerpts from Andrew Dunstan's message of mar sep 04 01:16:39 -0300 2012:
> 
> > And here's the first Windows buildfarm check of pg_upgrade. 
> > <http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=pitta&dt=2012-09-04%2003%3A00%3A05&stg=check-pg_upgrade>
> 
> Great, thanks.
> 
> Who's going to work now on porting the shell script to Perl? ;-)

Well, we require Perl for development, but not for usage, at least not
yet.  There was talk of needing Perl for doing standby pg_upgrade, but
there were too many concerns about that idea.

> Somehow the verbose reporting of user relation files being copied does
> not seem exceedingly useful; and I don't remember seeing that on Linux.
> 
> Should this be tweaked to avoid outputting the status message?
> 
> c:\mingw\msys\1.0\home\pgrunner\bf\root\HEAD\pgsql.7020\contrib\pg_upgrade>echo
> ECHO is on.

Probably.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_upgrade del/rmdir path fix
Next
From: Tom Lane
Date:
Subject: Re: 9.2rc1 produces incorrect results