Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > +# contrib/pg_upgrade/test.sh
> > +#
> > +# Test driver for pg_upgrade.  Initializes a new database cluster,
> > +# runs the regression tests (to put in some data), runs pg_dumpall,
> > +# runs pg_upgrade, runs pg_dumpall again, compares the dumps.
> 
> Hm .. my experience is that that doesn't work at all, because the
> regression tests set up assorted C functions whose implementations are
> in pg_regress.so, and it creates them with absolute path references
> to pg_regress.so.  When you try to load that into another installation
> that's a different version of PG, it quite properly fails.  So I think
> that as given, this script is only useful for testing pg_upgrade of
> $currentversion to $currentversion.  Which is surely better than no test

Reminder --- you can't use pg_upgrade to go from the same catalog
version to the same catalog version because the catalog version is
embedded in the tablespace directory name.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

In response to

• Re: pg_upgrade automatic testing at 2011-08-30 20:25:36 from Tom Lane

Responses

• Re: pg_upgrade automatic testing at 2011-09-02 14:36:01 from Peter Eisentraut

pgsql-hackers by date

Next:	From: Bruce Momjian	Date: 2011-09-01 23:10:57
	Subject: Re: pg_upgrade automatic testing
Previous:	From: Bruce Momjian	Date: 2011-09-01 22:02:22
	Subject: Re: strange row number estimates in pg9.1rc1