New upstream microreleases 9.3.20, 9.5.10 and 9.6.6

Bionic is already having 10.0-1 in proposed and will autosync 10.1-x as well as 9.6.6-1 as soon as it hits Debian (probably next week).

We are on a transition to take 9.6 out there - also Binoic is as far as possible from being released - so in this case no need to push to Bionic first for these MREs.

It would be great to have these packages prepared in proposed by then, especially since the autopkgtest queue will take a while atm - that would give it some time to build&test there.

This is (so far) based on the staging area, but that is usually ending up being
just an archive copy. So we should be good to start now.
Sniffing started in a Bileto Ticket.
- Trusty, Xenial, zesty, Artful: https://bileto.ubuntu.com/#/ticket/3029
- Bionic will be a sync once Debian picked 9.6.6-1 (and equiv to Artful)

TODO need to check the new News link like the old https://www.postgresql.org/about/news/1733 once available to check if there are important upgrade actions to take.
Announce of that will be on 9th of November.

So far tests hit some known issues lxd-testers and one about pgcluster setup in some tests needing to avoid blocked ports. Those are all fixed in later releases already and usually ignored on the SRU (:-/, but a tradeoff of time).

That said it seems all known good tests are good still - pushing for SRU review.

P.S. also the release is public now, so opening up the bug visibility.

These appear to fix security vulnerabilities. As such, I will release them as security updates instead of going through the SRU process.

This bug was fixed in the package postgresql-9.5 - 9.5.10-0ubuntu0.16.04

---------------
postgresql-9.5 (9.5.10-0ubuntu0.16.04) xenial-security; urgency=medium

  * New upstream release (LP: #1730661)
    - Previously, a race condition allowed some table rows to be omitted from
      the index. It may be necessary to reindex existing BRIN indexes to
      recover from past occurrences of this problem.
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.5/static/release-9-5-10.html

 -- Christian Ehrhardt <email address hidden> Tue, 07 Nov 2017 14:33:50 +0100

This bug was fixed in the package postgresql-9.6 - 9.6.6-0ubuntu0.17.10

---------------
postgresql-9.6 (9.6.6-0ubuntu0.17.10) artful-security; urgency=medium

  * New upstream release (LP: #1730661)
    - Previously, a race condition allowed some table rows to be omitted from
      the index. It may be necessary to reindex existing BRIN indexes to
      recover from past occurrences of this problem.
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.6/static/release-9-6-6.html

 -- Christian Ehrhardt <email address hidden> Tue, 07 Nov 2017 14:33:54 +0100

This bug was fixed in the package postgresql-9.3 - 9.3.20-0ubuntu0.14.04

---------------
postgresql-9.3 (9.3.20-0ubuntu0.14.04) trusty-security; urgency=medium

  * New upstream release (LP: #1730661)
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.3/static/release-9-3-20.html

 -- Christian Ehrhardt <email address hidden> Tue, 07 Nov 2017 14:33:47 +0100

This bug was fixed in the package postgresql-9.6 - 9.6.6-0ubuntu0.17.04

---------------
postgresql-9.6 (9.6.6-0ubuntu0.17.04) zesty-security; urgency=medium

  * New upstream release (LP: #1730661)
    - Previously, a race condition allowed some table rows to be omitted from
      the index. It may be necessary to reindex existing BRIN indexes to
      recover from past occurrences of this problem.
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.6/static/release-9-6-6.html

 -- Christian Ehrhardt <email address hidden> Tue, 07 Nov 2017 14:33:52 +0100