Code review comment for lp:~paelzer/britney/hints-ubuntu-trusty-postgresqlMREs

Looks like pitti fixed this trivially in https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-common.git/commit/?id=fc40fc34ce in the development release. Instead of ignoring all armhf test results, could this be cherry-picked into the next postgres MRE SRU instead? I think it would fix the failures, and then we'd still be able to catch armhf-related regressions in postgres instead, rather than the test effectively being turned off. Right now at least the test success (apart from the stderr) is being checked manually.