* New upstream release(s) (LP: #1815665)
- By default, panic instead of retrying after fsync() failure, to avoid
possible data corruption. A new server parameter "guc-data-sync-retry"
has been added to control this;
- d/p/pg-9.5-Disallow-setting-client_min_messages-higher-than-ERR.patch:
to retain SRU stability this patch reverts one of the changes which
disabled the error suppression by setting client_min_messages to
fatal or panic. Overall that means no change to the handling of
client_min_messages due to this upload.
- Details about these and many further changes can be found at: https://www.postgresql.org/docs/9.5/static/release-9-5-15.html https://www.postgresql.org/docs/9.5/static/release-9-5-16.html
-- Christian Ehrhardt <email address hidden> Tue, 12 Feb 2019 21:25:00 +0100
This bug was fixed in the package postgresql-9.5 - 9.5.16- 0ubuntu0. 16.04.1
--------------- 0ubuntu0. 16.04.1) xenial; urgency=medium
postgresql-9.5 (9.5.16-
* New upstream release(s) (LP: #1815665) sync-retry" 9.5-Disallow- setting- client_ min_messages- higher- than-ERR. patch: min_messages due to this upload. /www.postgresql .org/docs/ 9.5/static/ release- 9-5-15. html /www.postgresql .org/docs/ 9.5/static/ release- 9-5-16. html
- By default, panic instead of retrying after fsync() failure, to avoid
possible data corruption. A new server parameter "guc-data-
has been added to control this;
- d/p/pg-
to retain SRU stability this patch reverts one of the changes which
disabled the error suppression by setting client_min_messages to
fatal or panic. Overall that means no change to the handling of
client_
- Details about these and many further changes can be found at:
https:/
https:/
-- Christian Ehrhardt <email address hidden> Tue, 12 Feb 2019 21:25:00 +0100