desktop-packages team mailing list archive

[Launchpad Bug Tracker <1461425@xxxxxxxxxxxxxxxxxx>]

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 <martin.pitt@xxxxxxxxxx>  Wed, 03 Jun 2015 09:23:58
+0200

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1461425

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

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  Fix Released
Status in postgresql-9.1 source package in Precise:
  Fix Released
Status in postgresql-9.1 source package in Trusty:
  Fix Released
Status in postgresql-9.3 source package in Trusty:
  Fix Released
Status in postgresql-9.4 source package in Utopic:
  Fix Released
Status in postgresql-9.4 source package in Vivid:
  Fix Released
Status in postgresql-9.4 source package in Wily:
  Fix Released
Status in postgresql-9.1 package in Debian:
  Fix Released

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1461425/+subscriptions