Re: pg_upgrade automatic testing

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade automatic testing
Date: 2011-09-02 22:37:17
Message-ID: 1315003039.11695.9.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On fre, 2011-09-02 at 16:00 -0400, Andrew Dunstan wrote:
> Basically the idea is to stash away build and data dirs (after we've run
> regression, PL and contrib testing) for stable branches (via a command
> line option) and then test upgrading them. A trial run on the first part
> is currently running. Once I have that sorted out I'll work on the
> testing bit ;-)

It won't work, unless you have a solution for fixing the paths of the
shared library modules used by the regression tests.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-09-02 22:50:31 Re: pg_upgrade automatic testing
Previous Message Josh Kupershmidt 2011-09-02 22:05:02 Re: mb_regress.sh gripes