Re: ALTER TABLE lock downgrades have broken pg_upgrade - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: ALTER TABLE lock downgrades have broken pg_upgrade
Date
Msg-id cddab88a-3a2b-cc78-9107-78af1ab33f7d@2ndquadrant.com
Whole thread Raw
In response to Re: ALTER TABLE lock downgrades have broken pg_upgrade  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: ALTER TABLE lock downgrades have broken pg_upgrade  (Bruce Momjian <bruce@momjian.us>)
Re: ALTER TABLE lock downgrades have broken pg_upgrade  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 5/3/16 1:25 PM, Alvaro Herrera wrote:
> If we can put together a script that runs test.sh for various versions
> and then verifies the runs, we could use it in both buildfarm and
> coverage.

Not that that would be useless, but note that the value in this case 
(and most others) comes from having a candidate object in the database 
before upgrade that exercises the particular problem, mostly independent 
of what version you upgrade from and to.  So far the way to do that is 
to leave "junk" in the regression test database, but that's clearly a 
bit silly.

I think the way forward is to create a TAP test suite for pg_upgrade 
that specifically exercises a lot of scenarios with small purpose-built 
test databases.

Then, the problem of having to compare dump output across versions also 
goes away more easily.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Martín Marqués
Date:
Subject: Minor documentation patch
Next
From: Jim Nasby
Date:
Subject: Re: Add jsonb_compact(...) for whitespace-free jsonb to text