Skip site navigation (1) Skip section navigation (2)

Re: pg_upgrade automatic testing

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade automatic testing
Date: 2011-09-02 14:36:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On tor, 2011-09-01 at 18:55 -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > > +# contrib/pg_upgrade/
> > > +#
> > > +# 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, and it creates them with absolute path references
> > to  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.

Well, it does work, but only because the regression tests don't keep a
tablespace around at the end.  Would pg_upgrade complain otherwise?

In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2011-09-02 14:43:05
Subject: Re: pg_upgrade automatic testing
Previous:From: Kevin GrittnerDate: 2011-09-02 14:34:34
Subject: Re: postgresql.conf archive_command example

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group