Re: pg_upgrade automatic testing - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_upgrade automatic testing
Date
Msg-id 1322434422.29401.17.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: pg_upgrade automatic testing  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_upgrade automatic testing  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On lör, 2011-11-05 at 18:45 +0200, Peter Eisentraut wrote:
> On mån, 2011-09-19 at 07:06 +0300, Peter Eisentraut wrote:
> > I found a simpler way to get this working.  Just hack up the catalogs
> > for the new path directly.  So I can now run this test suite against
> > older versions as well, like this:
> > 
> > contrib/pg_upgrade$ make installcheck oldsrc=somewhere oldbindir=elsewhere
> 
> Any comments on how to proceed with this?  I think it has been useful in
> detecting pg_upgrade breakage a few times already, so I'd like to commit
> it and start using it.

I've committed it now, and some buildfarm members are failing with lack
of shared memory, semaphores, or disk space.  Don't know what to do with
that or why so many are failing like that.  We could create a way to
omit the test if it becomes a problem.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: hiding variable-length fields from Form_pg_* structs
Next
From: Tom Lane
Date:
Subject: Re: pg_upgrade automatic testing