Re: pg_upgrade fails to detect unsupported arrays and ranges
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Tomas Vondra <tomas.vondra@2ndquadrant.com>
Date: 2019-11-10T23:06:17Z
Lists: pgsql-hackers
Daniel Gustafsson <daniel@yesql.se> writes: > Applies, builds clean and passes light testing. Thanks for checking! > I can see the appeal of > including it before the wrap, even though I personally would've held off. Nah, I'm not gonna risk it at this stage. I concur with your point that this is an ancient bug, and one that is unlikely to bite many people. I'll push it Wednesday or so. regards, tom lane
Commits
-
Improve wording of some pg_upgrade failure reports.
- c9c37ae03fea 14.0 landed
-
Fix some more omissions in pg_upgrade's tests for non-upgradable types.
- 54a23307193c 9.6.22 landed
- d5722c92795d 10.17 landed
- bbcfee0e56a2 13.3 landed
- ba86371b9ca0 12.7 landed
- 57c081de0afc 14.0 landed
- 404946d40109 11.12 landed
-
Handle arrays and ranges in pg_upgrade's test for non-upgradable types.
- fb26754af4da 9.5.21 landed
- f378d4dac4ce 9.6.17 landed
- c443e3c43927 10.12 landed
- 8e4ef328738f 11.7 landed
- 56c06999d3c3 9.4.26 landed
- 29aeda6e4e60 13.0 landed
- 1cd57b05ef8b 12.2 landed