Given that it "only" failed during upgrade check, not the earlier parallel check, it is possible that it's entirely unrelated and just a low likelihood event?
May be, may be. So, we have bug with low probability.
This however does clearly seem related: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fulmar&dt=2018-04-07%2018%3A15%3A15 Probably caused by that animal using a non-standard collation?It should be already fixed in
https://git.postgresql.org/pg/commitdiff/01bb85169afadfe63e2f0e344ff671292080de7e -- Teodor Sigaev E-mail: teo...@sigaev.ru WWW: http://www.sigaev.ru/
