From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
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-04-07 21:03:12 |
Message-ID: | BANLkTimBfP8ju4k4ndwUs54E88CEoJhbeA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 7, 2011 at 4:02 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Seeing that 9.1-to-9.1 pg_upgrade has apparently been broken for months,
> it would probably be good to have some kind of automatic testing for it.
> Attached is something I hacked together that at least exposes the
> current problems, easily available by typing "make check" and waiting.
> It does not yet fully implement the full testing procedure in the
> TESTING file, in particular the diffing of the dumps (well, because you
> can't get there yet).
>
> Is that something that people are interested in refining?
>
> (I think it would even be possible under this setup to create special
> regression test cases that are only run under the pg_upgrade test run,
> to exercise particularly tricky upgrade cases.)
I think it's a worthwhile thing to do, but right now I think it would
be more helpful if you could help fix the breakage your patch created,
rather than working on new stuff.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2011-04-07 21:06:38 | Re: [COMMITTERS] pgsql: Add traceback information to PL/Python errors |
Previous Message | Robert Haas | 2011-04-07 21:01:41 | Re: [COMMITTERS] pgsql: Add traceback information to PL/Python errors |