This bug was fixed in the package postgresql-9.5 -
9.5.16-0ubuntu0.16.04.1
---
postgresql-9.5 (9.5.16-0ubuntu0.16.04.1) xenial; urgency=medium
* New upstream release(s) (LP: #1815665)
- By default, panic instead of retrying after fsync() failure, to avoid
possible data cor
This bug was fixed in the package postgresql-10 - 10.7-0ubuntu0.18.04.1
---
postgresql-10 (10.7-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1815665)
- By default, panic instead of retrying after fsync() failure, to avoid
possible data corruption.
This bug was fixed in the package postgresql-10 - 10.7-0ubuntu0.18.10.1
---
postgresql-10 (10.7-0ubuntu0.18.10.1) cosmic; urgency=medium
* New upstream release (LP: #1815665)
- By default, panic instead of retrying after fsync() failure, to avoid
possible data corruption.
** No longer affects: postgresql-plproxy (Ubuntu)
** No longer affects: postgresql-plproxy (Ubuntu Bionic)
** No longer affects: postgresql-plproxy (Ubuntu Cosmic)
** No longer affects: postgresql-rum (Ubuntu Cosmic)
** No longer affects: postgresql-rum (Ubuntu Bionic)
** No longer affects: pg
** No longer affects: postgresql-10 (Ubuntu)
** No longer affects: postgresql-9.5 (Ubuntu)
** No longer affects: skytools3 (Ubuntu Xenial)
** No longer affects: skytools3 (Ubuntu)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscrib
** Changed in: postgresql-11 (Ubuntu Disco)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1815665
T
This bug was fixed in the package pglogical-ticker - 1.3.1-1ubuntu1
---
pglogical-ticker (1.3.1-1ubuntu1) disco; urgency=medium
* d/p/fix-test-error-11.2.patch: Fix test issue with
postgresql 11.2 (LP: #1815665)
-- Christian Ehrhardt Mon, 11 Mar
2019 13:32:27 +0100
** Chang
After adapting the description for the new insights I uploaded the two
10.7 branches (Bionic/Cosmic) to the unapproved queue as well (9.5 for
Xenial was there already).
** Changed in: postgresql-10 (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: postgresql-10 (Ubuntu Bionic)
Due to the reverts this is much less disruptive, plenty of bug tasks got
invalid.
As 11.2 gets the change postgresql-rum in Disco is affected, but that is
already in 1.3.2-4 which is in Disco.
** Changed in: postgresql-rum (Ubuntu)
Status: New => Fix Released
** Changed in: postgresql-11
The error is due to this change [1]
While we could modify and rebuild postgresql-rum we don't know what else
people might have built against that which is not in the Archive.
This applies only to branches 11 (not yet released, so ok) and 10
(Bionic/Cosmic)
My suggestion would be to carry a rever
https://codesearch.debian.net/search?q=%5BSs%5D%5BEe%5D%5BTt%5D%5Cs*client_min_messages.*fatal
Not sure how I could search that way in a past release, but it gives some
confirming hits.
For our current case I can confirm the following issues being due to this:
- skytools3 (xenial, not in archive
11 matches
Mail list logo
