New upstream microreleases 9.1.17, 9.3.8, 9.4.3 - fixes regression in previous update

[Martin Pitt]

Upstream will push out new microreleases tomorrow after a pretty severe regression in the previous rounds of updates:

https://wiki.postgresql.org/wiki/May_2015_Fsync_Permissions_Bug#I.27ve_hit_this_bug_and_I_can.27t_restart_Postgres._What_do_I_do.3F

This particularly affects 9.1 due to the way we handle SSL certificates, i. e. Ubuntu 12.04. Later releases are much less affected as we don't have to symlink the certificate there any more.

SRU TEST CASE:

  * install postgresql-9.1
  * pkill -SEGV postgres
  * service postgresql start

With 9.1.16 this will fail with

The PostgreSQL server failed to start. Please check the log output:
2015-06-03 09:16:35 CEST LOG: database system was interrupted; last known up at 2015-06-03 09:15:27 CEST
2015-06-03 09:16:35 CEST FATAL: could not open file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
2015-06-03 09:16:35 CEST LOG: startup process (PID 10527) exited with exit code 1
2015-06-03 09:16:35 CEST LOG: aborting startup due to startup process failure

With 9.1.17 (or earlier versions than 9.1.16) this should succeed.

[Martin Pitt (pitti)]

All updates uploaded to the -proposed SRU review queues.

[Chris J Arges (arges)]

Hello Martin, or anyone else affected,

Accepted postgresql-9.3 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.3/9.3.8-0ubuntu0.4.04 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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

[Chris J Arges (arges)]

Hello Martin, or anyone else affected,

Accepted postgresql-9.1 into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.1/9.1.17-0ubuntu0.12.04 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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

[Chris J Arges (arges)]

Hello Martin, or anyone else affected,

Accepted postgresql-9.1 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.1/9.1.17-0ubuntu0.14.04 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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

[Chris J Arges (arges)]

Martin,
So I accidentally accepted postgresql-9.4_9.4.3-0ubuntu0.14.10 in utopic-proposed before wily was uploaded. I cancelled the build and removed the packages, so please re-upload this version when you can.
Thanks,

[Martin Pitt (pitti)]

wily will be synced from sid as soon as Christopher uploads it (presumably over the weekend, maybe on Monday); but I thought we could accept packages into -proposed before that, just not release them? Anyway, precise is the most urgent here, the others can wait for a bit.

[Martin Pitt (pitti)]

Utopic reuploaded with version bump: postgresql-9.4 9.4.3-0ubuntu0.14.10.1

[Martin Pitt (pitti)]

https://launchpad.net/ubuntu/+source/postgresql-9.4/9.4.3-1

[Ubuntu Foundations Team Bug Bot (crichton)]

As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of postgresql-9.3 from trusty-proposed was performed and bug 1462302 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and tag 1462302 "bot-stop-nagging". Thanks!

[Martin Pitt (pitti)]

I ran the test case (SEGV postmaster and restart) and confirm that it now works again with the -proposed packages. I also ran the autopkgtest on precise. Trusty's ran in CI: https://jenkins.qa.ubuntu.com/job/trusty-adt-postgresql-9.3/

[Chris J Arges (arges)]

Hello Martin, or anyone else affected,

Accepted postgresql-9.4 into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.4/9.4.3-0ubuntu0.14.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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

[Chris J Arges (arges)]

Hello Martin, or anyone else affected,

Accepted postgresql-9.4 into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.4/9.4.3-0ubuntu0.15.04 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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-9.1 - 9.1.17-0ubuntu0.12.04

---------------
postgresql-9.1 (9.1.17-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream bug fix release (LP: #1461425)
    - Avoid failures while fsync'ing data directory during crash restart.

      In the previous minor releases we added a patch to fsync everything in
      the data directory after a crash. Unfortunately its response to any
      error condition was to fail, thereby preventing the server from starting
      up, even when the problem was quite harmless. An example is that an
      unwritable file in the data directory would prevent restart on some
      platforms; but it is common to make SSL certificate files unwritable by
      the server. Revise this behavior so that permissions failures are
      ignored altogether, and other types of failures are logged but do not
      prevent continuing.

   - See release notes for details about other fixes.

 -- Martin Pitt <email address hidden> Wed, 03 Jun 2015 09:58:48 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-9.1 - 9.1.17-0ubuntu0.14.04

---------------
postgresql-9.1 (9.1.17-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1461425). No effective changes for
    PL/Perl, the version must just be higher than the one in precise, to not
    break upgrades.

 -- Martin Pitt <email address hidden> Wed, 03 Jun 2015 09:56:12 +0200

[Martin Pitt (pitti)]

https://jenkins.qa.ubuntu.com/job/utopic-adt-postgresql-9.4/ and https://jenkins.qa.ubuntu.com/job/vivid-adt-postgresql-9.4/ succeeded for 9.4.3.

Note the three test regressions for utopic:
https://jenkins.qa.ubuntu.com/job/utopic-adt-orafce/lastBuild/
https://jenkins.qa.ubuntu.com/job/utopic-adt-pgsql-asn1oid/lastBuild/
https://jenkins.qa.ubuntu.com/job/utopic-adt-skytools3/lastBuild/

They now fail because of
 + unrecognized value "all;" for "ECHO"; assuming "none"

This warning got introduced into the previous postgresql microrelease (9.4.2) already. The tests have an invalid semicolon after the "all", which got fixed in their trunks/debian unstable/wily etc., but not yet in the stable packages. It's not a functional regression.

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-9.3 - 9.3.8-0ubuntu0.4.04

---------------
postgresql-9.3 (9.3.8-0ubuntu0.4.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1461425)
    - Avoid failures while fsync'ing data directory during crash restart.

      In the previous minor releases we added a patch to fsync everything in
      the data directory after a crash. Unfortunately its response to any
      error condition was to fail, thereby preventing the server from starting
      up, even when the problem was quite harmless. An example is that an
      unwritable file in the data directory would prevent restart on some
      platforms; but it is common to make SSL certificate files unwritable by
      the server. Revise this behavior so that permissions failures are
      ignored altogether, and other types of failures are logged but do not
      prevent continuing.

   - See release notes for details about other fixes.

 -- Martin Pitt <email address hidden> Wed, 03 Jun 2015 09:54:24 +0200

[Chris J Arges (arges)]

The verification of the Stable Release Update for postgresql-9.3 has completed successfully and the package has now been 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.

[Martin Pitt (pitti)]

Note that in bug 1464669 the next round of PostgreSQL updates is already waiting.

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-9.4 - 9.4.3-0ubuntu0.14.10.1

---------------
postgresql-9.4 (9.4.3-0ubuntu0.14.10.1) utopic-proposed; urgency=medium

  * New upstream bug fix release (LP: #1461425)
    - Avoid failures while fsync'ing data directory during crash restart.

      In the previous minor releases we added a patch to fsync everything in
      the data directory after a crash. Unfortunately its response to any
      error condition was to fail, thereby preventing the server from starting
      up, even when the problem was quite harmless. An example is that an
      unwritable file in the data directory would prevent restart on some
      platforms; but it is common to make SSL certificate files unwritable by
      the server. Revise this behavior so that permissions failures are
      ignored altogether, and other types of failures are logged but do not
      prevent continuing.

   - See release notes for details about other fixes.

 -- Martin Pitt <email address hidden> Wed, 03 Jun 2015 09:30:17 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-9.4 - 9.4.3-0ubuntu0.15.04

---------------
postgresql-9.4 (9.4.3-0ubuntu0.15.04) vivid-proposed; urgency=medium

  * New upstream bug fix release (LP: #1461425)
    - Avoid failures while fsync'ing data directory during crash restart.

      In the previous minor releases we added a patch to fsync everything in
      the data directory after a crash. Unfortunately its response to any
      error condition was to fail, thereby preventing the server from starting
      up, even when the problem was quite harmless. An example is that an
      unwritable file in the data directory would prevent restart on some
      platforms; but it is common to make SSL certificate files unwritable by
      the server. Revise this behavior so that permissions failures are
      ignored altogether, and other types of failures are logged but do not
      prevent continuing.

   - See release notes for details about other fixes.

 -- Martin Pitt <email address hidden> Wed, 03 Jun 2015 09:23:58 +0200