| 2019-02-12 20:10:39 |
Christian Ehrhardt |
bug |
|
|
added bug |
| 2019-02-12 20:10:49 |
Christian Ehrhardt |
description |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Note: opening private as it is not yet announced
Public announce will on thursday. |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Note: opening private as it is not yet announced
Public announce will on thursday. |
|
| 2019-02-12 20:11:00 |
Christian Ehrhardt |
bug task added |
|
postgresql-9.5 (Ubuntu) |
|
| 2019-02-12 20:11:07 |
Christian Ehrhardt |
bug task added |
|
postgresql-11 (Ubuntu) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Disco |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-9.5 (Ubuntu Disco) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-10 (Ubuntu Disco) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-11 (Ubuntu Disco) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Xenial |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-9.5 (Ubuntu Xenial) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-10 (Ubuntu Xenial) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-11 (Ubuntu Xenial) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-9.5 (Ubuntu Bionic) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-10 (Ubuntu Bionic) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-11 (Ubuntu Bionic) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-9.5 (Ubuntu Cosmic) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-10 (Ubuntu Cosmic) |
|
| 2019-02-12 20:11:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-11 (Ubuntu Cosmic) |
|
| 2019-02-12 20:12:03 |
Christian Ehrhardt |
bug task deleted |
postgresql-10 (Ubuntu Xenial) |
|
|
| 2019-02-12 20:12:09 |
Christian Ehrhardt |
bug task deleted |
postgresql-10 (Ubuntu Disco) |
|
|
| 2019-02-12 20:12:18 |
Christian Ehrhardt |
bug task deleted |
postgresql-11 (Ubuntu Cosmic) |
|
|
| 2019-02-12 20:12:22 |
Christian Ehrhardt |
bug task deleted |
postgresql-11 (Ubuntu Bionic) |
|
|
| 2019-02-12 20:12:27 |
Christian Ehrhardt |
bug task deleted |
postgresql-11 (Ubuntu Xenial) |
|
|
| 2019-02-12 20:12:35 |
Christian Ehrhardt |
bug task deleted |
postgresql-9.5 (Ubuntu Bionic) |
|
|
| 2019-02-12 20:12:43 |
Christian Ehrhardt |
bug task deleted |
postgresql-9.5 (Ubuntu Cosmic) |
|
|
| 2019-02-12 20:12:47 |
Christian Ehrhardt |
bug task deleted |
postgresql-9.5 (Ubuntu Disco) |
|
|
| 2019-02-12 20:15:27 |
Christian Ehrhardt |
postgresql-11 (Ubuntu Disco): status |
New |
Confirmed |
|
| 2019-02-12 20:15:30 |
Christian Ehrhardt |
postgresql-9.5 (Ubuntu Xenial): status |
New |
Triaged |
|
| 2019-02-12 20:15:32 |
Christian Ehrhardt |
postgresql-10 (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2019-02-12 20:15:34 |
Christian Ehrhardt |
postgresql-10 (Ubuntu Bionic): status |
New |
Triaged |
|
| 2019-02-12 20:15:38 |
Christian Ehrhardt |
postgresql-9.5 (Ubuntu): status |
New |
Invalid |
|
| 2019-02-12 20:15:41 |
Christian Ehrhardt |
postgresql-10 (Ubuntu): status |
New |
Invalid |
|
| 2019-02-12 20:55:18 |
Christian Ehrhardt |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/postgresql-9.5/+git/postgresql-9.5/+merge/363094 |
|
| 2019-02-12 22:35:56 |
Christian Ehrhardt |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/postgresql-10/+git/postgresql-10/+merge/363098 |
|
| 2019-02-12 22:36:20 |
Christian Ehrhardt |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/postgresql-10/+git/postgresql-10/+merge/363099 |
|
| 2019-02-13 10:29:58 |
Christian Ehrhardt |
description |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Note: opening private as it is not yet announced
Public announce will on thursday. |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Regression potential:
- usually this works smoothly, but this time there is a change worth to
mention for the SRU team. There is a change in all branches like [1]
I agree with the change - it is right to fix the FE/BE protocol, the
only thing that should be affected are testcases like the ones I found.
So maybe some CIs (checking expected vs actual output) might break and
logs might increase (now tracking formerly ignored errors), but
not more.
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910 |
|
| 2019-02-13 10:30:23 |
Christian Ehrhardt |
information type |
Private |
Public |
|
| 2019-02-13 11:02:53 |
Christian Ehrhardt |
bug task added |
|
skytools3 (Ubuntu) |
|
| 2019-02-13 11:03:41 |
Christian Ehrhardt |
bug task added |
|
pg-repack (Ubuntu) |
|
| 2019-02-13 11:04:59 |
Christian Ehrhardt |
bug task added |
|
postgresql-plproxy (Ubuntu) |
|
| 2019-02-13 11:05:20 |
Christian Ehrhardt |
bug task added |
|
postgresql-rum (Ubuntu) |
|
| 2019-02-13 11:05:34 |
Christian Ehrhardt |
bug task added |
|
pg-partman (Ubuntu) |
|
| 2019-02-13 11:07:44 |
Christian Ehrhardt |
pg-repack (Ubuntu): status |
New |
Invalid |
|
| 2019-02-13 11:07:55 |
Christian Ehrhardt |
pg-partman (Ubuntu): status |
New |
Invalid |
|
| 2019-02-13 11:08:06 |
Christian Ehrhardt |
pg-repack (Ubuntu Bionic): status |
New |
Triaged |
|
| 2019-02-13 11:08:17 |
Christian Ehrhardt |
pg-repack (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2019-02-13 11:09:30 |
Christian Ehrhardt |
postgresql-plproxy (Ubuntu): status |
New |
Invalid |
|
| 2019-02-13 11:09:41 |
Christian Ehrhardt |
postgresql-rum (Ubuntu): status |
New |
Invalid |
|
| 2019-02-13 11:09:52 |
Christian Ehrhardt |
skytools3 (Ubuntu): status |
New |
Invalid |
|
| 2019-02-13 11:10:00 |
Christian Ehrhardt |
skytools3 (Ubuntu Xenial): status |
New |
Triaged |
|
| 2019-02-13 11:10:14 |
Christian Ehrhardt |
postgresql-plproxy (Ubuntu Bionic): status |
New |
Triaged |
|
| 2019-02-13 11:10:23 |
Christian Ehrhardt |
postgresql-plproxy (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2019-02-13 12:09:35 |
Christian Ehrhardt |
pg-partman (Ubuntu Cosmic): status |
New |
Invalid |
|
| 2019-03-06 13:44:38 |
Christian Ehrhardt |
description |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Regression potential:
- usually this works smoothly, but this time there is a change worth to
mention for the SRU team. There is a change in all branches like [1]
I agree with the change - it is right to fix the FE/BE protocol, the
only thing that should be affected are testcases like the ones I found.
So maybe some CIs (checking expected vs actual output) might break and
logs might increase (now tracking formerly ignored errors), but
not more.
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910 |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Regression potential:
- usually this works smoothly except a few test hickups that need to be
clarified to be sure. But this time there are changes worth to
mention for the SRU team.
- change [1] is in all branches and after coordinating with Debian and
Upstream and some members of the SRU Team (Malta) we decided to revert
this change in all releases that get SRUs (So 11.x in Disco is the
only who will get it).
- Furthermore [2] is only in the 10.x branch (Bionic/Cosmic) and will
change the ABI. After discussion with upstream and the SRU Team we
want to avoid that the ABI (for extensions) differes between diffrent
10.7 out in the wild. Therefore we will rework the affected extensions
in the archive and try to scan for out of archive extensions before
upgrading bailing out in preinst (That has to be proven to work
reliably)
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910
[2]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b2e754c14 |
|
| 2019-03-06 13:55:35 |
Christian Ehrhardt |
postgresql-9.5 (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2019-03-06 14:46:25 |
Christian Ehrhardt |
description |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Regression potential:
- usually this works smoothly except a few test hickups that need to be
clarified to be sure. But this time there are changes worth to
mention for the SRU team.
- change [1] is in all branches and after coordinating with Debian and
Upstream and some members of the SRU Team (Malta) we decided to revert
this change in all releases that get SRUs (So 11.x in Disco is the
only who will get it).
- Furthermore [2] is only in the 10.x branch (Bionic/Cosmic) and will
change the ABI. After discussion with upstream and the SRU Team we
want to avoid that the ABI (for extensions) differes between diffrent
10.7 out in the wild. Therefore we will rework the affected extensions
in the archive and try to scan for out of archive extensions before
upgrading bailing out in preinst (That has to be proven to work
reliably)
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910
[2]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b2e754c14 |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Regression potential:
- usually this works smoothly except a few test hickups that need to be
clarified to be sure. But this time there are changes worth to
mention for the SRU team.
- change [1] is in all branches Xenil/Bionic/Cosmic and after
coordinating with Debian and Upstream and some members of the SRU Team
(Malta) and Debian we decided to revert this change in all releases
that get SRUs (So 11.x in Disco is the only who will get it).
Users are either:
a) not affected at all and therefore are fine as-is (majority)
b) not affected by the problem but have tests/scripts/CI/... that
rely on the behavior (we don't want to SRU break them)
c) have a case that is affected, in that case the "code using
client_min_messages" is the one to be considered broken (in favor
of the majority of users) and that code should be changed in stead
of postgres.
Furthermore with that decision we are also in sync with Debian
handling the same
- Change [2] renaming of symbols rb/rbt is fine doing forward (Disco),
but not in Bionic/Cosmic as we'd break en external ABI of the past in
an SRU
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910
[2]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b2e754c14 |
|
| 2019-03-07 14:27:10 |
Christian Ehrhardt |
description |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Regression potential:
- usually this works smoothly except a few test hickups that need to be
clarified to be sure. But this time there are changes worth to
mention for the SRU team.
- change [1] is in all branches Xenil/Bionic/Cosmic and after
coordinating with Debian and Upstream and some members of the SRU Team
(Malta) and Debian we decided to revert this change in all releases
that get SRUs (So 11.x in Disco is the only who will get it).
Users are either:
a) not affected at all and therefore are fine as-is (majority)
b) not affected by the problem but have tests/scripts/CI/... that
rely on the behavior (we don't want to SRU break them)
c) have a case that is affected, in that case the "code using
client_min_messages" is the one to be considered broken (in favor
of the majority of users) and that code should be changed in stead
of postgres.
Furthermore with that decision we are also in sync with Debian
handling the same
- Change [2] renaming of symbols rb/rbt is fine doing forward (Disco),
but not in Bionic/Cosmic as we'd break en external ABI of the past in
an SRU
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910
[2]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b2e754c14 |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Regression potential:
- usually this works smoothly except a few test hickups that need to be
clarified to be sure. But this time there are changes worth to
mention for the SRU team.
- change [1] is in all branches Xenil/Bionic/Cosmic and after
coordinating with Debian and Upstream and some members of the SRU Team
(Malta) and Debian we decided to revert this change in all releases
that get SRUs (So 11.x in Disco is the only who will get it).
If misused not having that fix could cause bad data.
But users of Ubuntu are either:
a) not affected at all and therefore are fine as-is (majority)
b) not affected by the problem but have tests/scripts/CI/... that
rely on the behavior (we don't want to SRU break them)
c) have a case that is affected, in that case the "code using
client_min_messages" is the one to be considered broken (in favor
of the majority of users) and that code should be changed instead
of PostgreSQL.
Furthermore with that decision we are also in sync with Debian
handling the same
- Change [2] renaming of symbols rb/rbt is fine doing forward (Disco),
but not in Bionic/Cosmic as we'd break en external ABI of the past in
an SRU. Please Note that the offending plruby this change was made for
is not even in the Archive.
=> Especially in regard to "regression potential" that means that we will
NOT apply the two changes that are somewhat discussion-worthy. We
might in later updates reconsider them, but for now when applying the
latest stable release we revert those two primarily for the reason to
have the lowest possible regression potential for the SRU.
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910
[2]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b2e754c14 |
|
| 2019-03-07 14:28:32 |
Christian Ehrhardt |
description |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Regression potential:
- usually this works smoothly except a few test hickups that need to be
clarified to be sure. But this time there are changes worth to
mention for the SRU team.
- change [1] is in all branches Xenil/Bionic/Cosmic and after
coordinating with Debian and Upstream and some members of the SRU Team
(Malta) and Debian we decided to revert this change in all releases
that get SRUs (So 11.x in Disco is the only who will get it).
If misused not having that fix could cause bad data.
But users of Ubuntu are either:
a) not affected at all and therefore are fine as-is (majority)
b) not affected by the problem but have tests/scripts/CI/... that
rely on the behavior (we don't want to SRU break them)
c) have a case that is affected, in that case the "code using
client_min_messages" is the one to be considered broken (in favor
of the majority of users) and that code should be changed instead
of PostgreSQL.
Furthermore with that decision we are also in sync with Debian
handling the same
- Change [2] renaming of symbols rb/rbt is fine doing forward (Disco),
but not in Bionic/Cosmic as we'd break en external ABI of the past in
an SRU. Please Note that the offending plruby this change was made for
is not even in the Archive.
=> Especially in regard to "regression potential" that means that we will
NOT apply the two changes that are somewhat discussion-worthy. We
might in later updates reconsider them, but for now when applying the
latest stable release we revert those two primarily for the reason to
have the lowest possible regression potential for the SRU.
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910
[2]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b2e754c14 |
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
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
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through SRU/Security as applicable.
Regression potential:
- usually this works smoothly except a few test hickups that need to be
clarified to be sure. But this time there are changes worth to
mention for the SRU team.
- change [1] is in all branches Xenil/Bionic/Cosmic and after
coordinating with Debian and Upstream and some members of the SRU Team
(Malta) and Debian we decided to revert this change in all releases
that get SRUs (So 11.x in Disco is the only who will get it).
What makes this slightly more important is that: if
client_min_messages is misused, then not having that fix
could cause bad data.
But users of Ubuntu are either:
a) not affected at all and therefore are fine as-is (majority)
b) not affected by the problem but have tests/scripts/CI/... that
rely on the behavior (we don't want to SRU break them)
c) have a case that is affected, in that case the "code using
client_min_messages" is the one to be considered broken (in favor
of the majority of users) and that code should be changed instead
of PostgreSQL.
Furthermore with that decision we are also in sync with Debian
handling the same
- Change [2] renaming of symbols rb/rbt is fine doing forward (Disco),
but not in Bionic/Cosmic as we'd break en external ABI of the past in
an SRU. Please Note that the offending plruby this change was made for
is not even in the Archive.
=> Especially in regard to "regression potential" that means that we will
NOT apply the two changes that are somewhat discussion-worthy. We
might in later updates reconsider them, but for now when applying the
latest stable release we revert those two primarily for the reason to
have the lowest possible regression potential for the SRU.
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910
[2]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b2e754c14 |
|
| 2019-03-08 08:22:57 |
Christian Ehrhardt |
postgresql-10 (Ubuntu Cosmic): status |
Triaged |
In Progress |
|
| 2019-03-08 08:23:08 |
Christian Ehrhardt |
postgresql-10 (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2019-03-08 08:23:17 |
Christian Ehrhardt |
pg-repack (Ubuntu Bionic): status |
Triaged |
Invalid |
|
| 2019-03-08 08:23:25 |
Christian Ehrhardt |
pg-repack (Ubuntu Cosmic): status |
Triaged |
Invalid |
|
| 2019-03-08 08:23:38 |
Christian Ehrhardt |
postgresql-plproxy (Ubuntu Bionic): status |
Triaged |
Invalid |
|
| 2019-03-08 08:23:59 |
Christian Ehrhardt |
postgresql-plproxy (Ubuntu Cosmic): status |
Triaged |
Invalid |
|
| 2019-03-08 08:24:09 |
Christian Ehrhardt |
postgresql-rum (Ubuntu): status |
Invalid |
New |
|
| 2019-03-08 08:24:16 |
Christian Ehrhardt |
postgresql-rum (Ubuntu Bionic): status |
New |
Invalid |
|
| 2019-03-08 08:24:24 |
Christian Ehrhardt |
postgresql-rum (Ubuntu Cosmic): status |
New |
Invalid |
|
| 2019-03-08 08:24:35 |
Christian Ehrhardt |
skytools3 (Ubuntu Xenial): status |
Triaged |
Invalid |
|
| 2019-03-08 08:26:11 |
Christian Ehrhardt |
postgresql-rum (Ubuntu): status |
New |
Fix Released |
|
| 2019-03-08 08:26:31 |
Christian Ehrhardt |
postgresql-11 (Ubuntu Disco): importance |
Undecided |
Critical |
|
| 2019-03-08 08:27:08 |
Christian Ehrhardt |
bug task added |
|
pglogical-ticker (Ubuntu) |
|
| 2019-03-08 08:27:19 |
Christian Ehrhardt |
pglogical-ticker (Ubuntu): importance |
Undecided |
Critical |
|
| 2019-03-08 08:27:19 |
Christian Ehrhardt |
pglogical-ticker (Ubuntu): status |
New |
Confirmed |
|
| 2019-03-11 17:45:54 |
Launchpad Janitor |
pglogical-ticker (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2019-03-11 19:23:03 |
Christian Ehrhardt |
postgresql-11 (Ubuntu Disco): status |
Confirmed |
Fix Released |
|
| 2019-03-28 13:19:34 |
Robie Basak |
postgresql-9.5 (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2019-03-28 13:19:39 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-03-28 13:19:41 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2019-03-28 13:19:45 |
Robie Basak |
tags |
|
verification-needed verification-needed-xenial |
|
| 2019-03-28 13:46:57 |
Robie Basak |
postgresql-10 (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-03-28 13:47:02 |
Robie Basak |
tags |
verification-needed verification-needed-xenial |
verification-needed verification-needed-bionic verification-needed-xenial |
|
| 2019-03-28 13:51:44 |
Robie Basak |
postgresql-10 (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2019-03-28 13:51:48 |
Robie Basak |
tags |
verification-needed verification-needed-bionic verification-needed-xenial |
verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
|
| 2019-03-29 09:33:55 |
Christian Ehrhardt |
tags |
verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
verification-done-bionic verification-done-cosmic verification-needed verification-needed-xenial |
|
| 2019-04-01 02:52:11 |
Mathew Hodson |
bug task deleted |
postgresql-10 (Ubuntu) |
|
|
| 2019-04-01 02:52:40 |
Mathew Hodson |
bug task deleted |
postgresql-9.5 (Ubuntu) |
|
|
| 2019-04-01 02:56:43 |
Mathew Hodson |
bug task deleted |
skytools3 (Ubuntu Xenial) |
|
|
| 2019-04-01 02:56:54 |
Mathew Hodson |
bug task deleted |
skytools3 (Ubuntu) |
|
|
| 2019-04-01 04:15:50 |
Mathew Hodson |
bug task deleted |
postgresql-plproxy (Ubuntu) |
|
|
| 2019-04-01 04:15:59 |
Mathew Hodson |
bug task deleted |
postgresql-plproxy (Ubuntu Bionic) |
|
|
| 2019-04-01 04:16:08 |
Mathew Hodson |
bug task deleted |
postgresql-plproxy (Ubuntu Cosmic) |
|
|
| 2019-04-01 04:16:54 |
Mathew Hodson |
bug task deleted |
postgresql-rum (Ubuntu Cosmic) |
|
|
| 2019-04-01 04:17:03 |
Mathew Hodson |
bug task deleted |
postgresql-rum (Ubuntu Bionic) |
|
|
| 2019-04-01 04:17:14 |
Mathew Hodson |
bug task deleted |
pg-repack (Ubuntu Cosmic) |
|
|
| 2019-04-01 04:17:22 |
Mathew Hodson |
bug task deleted |
pg-repack (Ubuntu Bionic) |
|
|
| 2019-04-01 04:17:29 |
Mathew Hodson |
bug task deleted |
pg-repack (Ubuntu) |
|
|
| 2019-04-01 04:17:38 |
Mathew Hodson |
bug task deleted |
pg-partman (Ubuntu Cosmic) |
|
|
| 2019-04-01 04:17:46 |
Mathew Hodson |
bug task deleted |
pg-partman (Ubuntu) |
|
|
| 2019-04-01 07:29:37 |
Christian Ehrhardt |
tags |
verification-done-bionic verification-done-cosmic verification-needed verification-needed-xenial |
verification-done verification-done-bionic verification-done-cosmic verification-done-xenial |
|
| 2019-04-01 07:38:14 |
Christian Ehrhardt |
branch linked |
|
lp:~paelzer/britney/hints-ubuntu-xenial-i386-libreoffice |
|
| 2019-04-04 08:52:50 |
Launchpad Janitor |
postgresql-10 (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-04-04 08:52:56 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-04-04 09:27:09 |
Launchpad Janitor |
postgresql-10 (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-04-04 10:04:44 |
Launchpad Janitor |
postgresql-9.5 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
