| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, buschmann(at)nidsa(dot)net, pgsql-hackers(at)lists(dot)postgresql(dot)org, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: pg_upgrade test for binary compatibility of core data types |
| Date: | 2021-01-15 08:00:31 |
| Message-ID: | d9f14840-9f6e-183d-f43a-9f9b9e1b6d19@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 2021-01-12 22:44, Andrew Dunstan wrote:
> Cross version pg_upgrade is tested regularly in the buildfarm, but not
> using test.sh. Instead it uses the saved data repository from a previous
> run of the buildfarm client for the source branch, and tries to upgrade
> that to the target branch.
Does it maintain a set of fixups similar to what is in test.sh? Are
those two sets the same?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-01-15 08:23:00 | BUG #16826: Regex in substring(... from ..) wrong |
| Previous Message | PG Bug reporting form | 2021-01-15 07:48:31 | BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2021-01-15 08:29:40 | Re: Wrong HINT during database recovery when occur a minimal wal. |
| Previous Message | Peter Eisentraut | 2021-01-15 07:56:27 | Re: Is it worth accepting multiple CRLs? |