Debdiffs LGTM. For the tests: postfix tests are a bit flaky. But the pg_repack regression should be investigated more seriously, that doesn't look like a flake at all (it also happened on all architectures):
2017-02-14 11:07:37 UTC [2371-1] ubuntu@contrib_regression ERROR: could not create unique index "idx_badindex_n" 2017-02-14 11:07:37 UTC [2371-2] ubuntu@contrib_regression DETAIL: Key (n)=(10) is duplicated. That seems very much related to the prominent fix in that release: + - Fix a race condition that could cause indexes built with CREATE INDEX + CONCURRENTLY to be corrupt (Pavan Deolasee, Tom Lane). + If CREATE INDEX CONCURRENTLY was used to build an index that depends on + a column not previously indexed, then rows inserted or updated by + transactions that ran concurrently with the CREATE INDEX command could + have received incorrect index entries. I suggest asking on https://www.postgresql.org/list/pgsql-bugs/ or that packager ML you recently joined. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664478 Title: New upstream microreleases 9.3.16, 9.5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.3/+bug/1664478/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
