Re: pg_upgrade automatic testing

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade automatic testing
Date: 2011-11-27 22:53:42
Message-ID: 1322434422.29401.17.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2011-11-27 23:03:38 Re: pgsql: Move pg_dump memory routines into pg_dumpmem.c/h and restore com
Previous Message Peter Eisentraut 2011-11-27 22:49:46 hiding variable-length fields from Form_pg_* structs