From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade automatic testing |
Date: | 2011-11-10 20:24:55 |
Message-ID: | 201111102024.pAAKOtD18135@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 don't have a problem with adding it.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-11-10 20:29:44 | Re: foreign key locks, 2nd attempt |
Previous Message | Kevin Grittner | 2011-11-10 20:24:48 | Re: const correctness |