New upstream microreleases 10.20, 12.10, 13.6 and 14.2

[Sergio Durigan Junior]

[Impact]

 * MRE for latest stable fixes of Postgres released on February 2022

[Test Case]

 * The Postgres MREs traditionally rely on the large set of autopkgtests
   to run for verification. In a PPA those are all already pre-checked to
   be good for this upload.

[Regression Potential]

 * Upstreams tests are usually great and in additon in the Archive there
   are plenty of autopkgtests that in the past catched issues before being
   released.
   But nevertheless there always is a risk for something to break. Since
   these are general stable releases I can't pinpoint them to a most-likely
   area.
   - usually this works smoothly except a few test hickups (flaky) that need to be
     clarified to be sure. Pre-checks will catch those to be discussed upfront (as last time)

[Other Info]

 * This is a reoccurring MRE, see below and all the references
 * CVEs this time:
   - None

Current versions in supported releases that got updates:
 postgresql-10 | 10.19-0ubuntu0.18.04.1 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x
 postgresql-12 | 12.9-0ubuntu0.20.04.1 | focal-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 postgresql-13 | 13.5-0ubuntu0.21.10.1 | impish-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x

Special cases:
- Jammy has already synced from Debian as usual (14.2).

Standing MRE - Consider last updates as template:
- pad.lv/1637236
- pad.lv/1664478
- pad.lv/1690730
- pad.lv/1713979
- pad.lv/1730661
- pad.lv/1747676
- pad.lv/1752271
- pad.lv/1786938
- pad.lv/1815665
- pad.lv/1828012
- pad.lv/1833211
- pad.lv/1839058
- pad.lv/1863108
- pad.lv/1892335
- pad.lv/1915254
- pad.lv/1928773
- pad.lv/1939396
- pad.lv/1950268

As usual we test and prep from the PPA and then push through SRU/Security as applicable.

[Sergio Durigan Junior (sergiodj)]

autopkgtest results for postgresql-13 are good:

Results from https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4785/?format=plain:
  postgresql-13 @ amd64:
    17.02.22 17:03:57 Log 🗒️ ✅ Triggers: ['postgresql-13/13.6-0ubuntu0.21.10.1~ppa1']
  postgresql-13 @ arm64:
    17.02.22 17:15:12 Log 🗒️ ✅ Triggers: ['postgresql-13/13.6-0ubuntu0.21.10.1~ppa1']
  postgresql-13 @ armhf:
    17.02.22 16:55:24 Log 🗒️ ✅ Triggers: ['postgresql-13/13.6-0ubuntu0.21.10.1~ppa1']
  postgresql-13 @ ppc64el:
    17.02.22 16:47:06 Log 🗒️ ✅ Triggers: ['postgresql-13/13.6-0ubuntu0.21.10.1~ppa1']
  postgresql-13 @ s390x:
    17.02.22 16:47:00 Log 🗒️ ✅ Triggers: ['postgresql-13/13.6-0ubuntu0.21.10.1~ppa1']

I am working on creating gbp repositories for the postgresql-{10,12,13,14} packages; once that is done, I will file an MP to update postgresql-13.

[Christian Ehrhardt  (paelzer)]

Thanks - That is good as a sniff test, but as I've mentioned the real test is when the hundreds of autopkgtest-enabled dependencies of postgres run in autopkgtest. Since currently the queues are rather full we agreed to do this directly in the SRU-upload and not pre-run all of these (as we'd surely do when this would go in via -security bypassing those tests otherwise).

[Sergio Durigan Junior (sergiodj)]

On Friday, February 18 2022, Christian Ehrhardt  wrote:

> Thanks - That is good as a sniff test, but as I've mentioned the real
> test is when the hundreds of autopkgtest-enabled dependencies of
> postgres run in autopkgtest. Since currently the queues are rather full
> we agreed to do this directly in the SRU-upload and not pre-run all of
> these (as we'd surely do when this would go in via -security bypassing
> those tests otherwise).

Yes, for sure.

--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14

[Sergio Durigan Junior (sergiodj)]

All packages have been uploaded and are now waiting for review/approval.

[Brian Murray (brian-murray)]

Hello Sergio, or anyone else affected,

Accepted postgresql-13 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-13/13.6-0ubuntu0.21.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Sergio Durigan Junior (sergiodj)]

As usual with non-security updates, we use the results of autopkgtest in order to perform the verification. In this case, all tests succeeded for postgresql-13 in Impish. Therefore, tagging as verification-done-impish.

[Chris Halse Rogers (raof)]

The verification of the Stable Release Update for postgresql-13 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-13 - 13.6-0ubuntu0.21.10.1

---------------
postgresql-13 (13.6-0ubuntu0.21.10.1) impish; urgency=medium

  * New upstream version (LP: #1961127).

    + A dump/restore is not required for those running 13.X.

    + However, if you have applied REINDEX CONCURRENTLY to a TOAST table's
      index, or observe failures to access TOAST datums, there has been a
      fix for this problem. Any existing corrupted indexes can be repaired
      by reindexing again.

    + Also, if you are upgrading from a version earlier than 13.5,
      see those release notes as well please.

    + Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/13/release-13-6.html

 -- Sergio Durigan Junior <email address hidden> Wed, 16 Feb 2022 21:17:27 -0500

[Christian Ehrhardt  (paelzer)]

Thanks for the status update Athos, to be clear those two are waiting for the SRU team in bionic/focal-unapproved since 2022-02-24.

[Chris Halse Rogers (raof)]

Hello Sergio, or anyone else affected,

Accepted postgresql-12 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-12/12.10-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted postgresql-12 (12.10-0ubuntu0.20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

check-postgres/2.25.0-1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#postgresql-12

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Athos Ribeiro (athos-ribeiro)]

As usual with non-security updates, we use the results of autopkgtest in order to perform the verification. In this case, all tests succeeded for postgresql-12 in Focal. Therefore, tagging as verification-done-focal.

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-12 - 12.10-0ubuntu0.20.04.1

---------------
postgresql-12 (12.10-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream version (LP: #1961127).

    + A dump/restore is not required for those running 12.X.

    + However, if you have applied REINDEX CONCURRENTLY to a TOAST table's
      index, or observe failures to access TOAST datums, there has been a
      fix for this problem. Any existing corrupted indexes can be repaired
      by reindexing again.

    + Also, if you are upgrading from a version earlier than 12.9, see
      those release notes as well please.

    + Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/12/release-12-10.html

 -- Athos Ribeiro <email address hidden> Wed, 23 Feb 2022 08:36:18 -0300

[Brian Murray (brian-murray)]

Hello Sergio, or anyone else affected,

Accepted postgresql-10 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-10/10.20-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted postgresql-10 (10.20-0ubuntu0.18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

redmine/3.4.4-1ubuntu0.1 (i386, amd64)
postfix/3.3.0-1ubuntu0.4 (i386)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#postgresql-10

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Athos Ribeiro (athos-ribeiro)]

As usual with non-security updates, we use the results of autopkgtest in order to perform the verification. In this case, all tests succeeded for postgresql-10 in Bionic. Therefore, tagging as verification-done-bionic.

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-10 - 10.20-0ubuntu0.18.04.1

---------------
postgresql-10 (10.20-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream version (LP: #1961127).

    + A dump/restore is not required for those running 10.X.

    + However, if you are upgrading from a version earlier than 10.19, see
      those release notes as well please.

    + The PostgreSQL community will stop releasing updates for the 10.X
      release series in November 2022. After this date, there will be no
      further minor release updates, but Ubuntu will continue to backport
      important fixes as needed.

    + Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/10/release-10-20.html

 -- Athos Ribeiro <email address hidden> Mon, 14 Feb 2022 10:28:53 -0300