Update all supported postgresql versions (Fixes CVE-2018-16850)#49906
Merged
c0bw3b merged 6 commits intoNixOS:stagingfrom Nov 14, 2018
Merged
Update all supported postgresql versions (Fixes CVE-2018-16850)#49906c0bw3b merged 6 commits intoNixOS:stagingfrom
c0bw3b merged 6 commits intoNixOS:stagingfrom
Conversation
Member
Author
|
postgresql-10 (and less probable postgresql-11) users using |
GrahamcOfBorg
added
10.rebuild-darwin: 101-500
|
Success on aarch64-linux (full log) Attempted: postgresql_10, postgresql_11, postgresql_9_3, postgresql_9_4, postgresql_9_5, postgresql_9_6 Partial log (click to expand)
|
|
Success on x86_64-linux (full log) Attempted: postgresql_10, postgresql_11, postgresql_9_3, postgresql_9_4, postgresql_9_5, postgresql_9_6 Partial log (click to expand)
|
c0bw3b
added
the
1.severity: security
Member
This is really the traditional mechanism for doing upgrades on extensions, but yes, I don't know of any way to force it. I don't even think e.g. Debian/Ubuntu packages will do any forced alterations like this (after all, you could have completely changed the permissions for all connected users, and any automated scripts couldn't know this a priori.) It might be best just to post an update to Discourse? Or maybe we should have some better news feed for things like this... |
thoughtpolice
approved these changes
Nov 8, 2018
Member
Author
|
Yes, sure, it is quite standard to do on when updating postgresql with extensions. While reading the update recommendations on the release note, I just told myself that when ported to This was just a remark, and I’ll probably drop a discourse comment about that. |
Contributor
|
Maybe this should target |
lsix
force-pushed
the
update_postgresql
branch
from
55199fb to
528978f
Compare
lsix
requested review from
Ericson2314,
FRidh,
edolstra,
matthewbauer,
nbp and
zimbatm
as code owners
Member
Author
|
@c0bw3b I have just rebased to staging a changed the PR's base. |
GrahamcOfBorg
added
6.topic: erlang
GrahamcOfBorg
removed
6.topic: fetch
See https://www.postgresql.org/about/news/1905/ for release information. Fixes CVE-2018-16850
See https://www.postgresql.org/about/news/1905/ for release information. Fixes CVE-2018-16850
See https://www.postgresql.org/about/news/1905/ for release information. Fixes CVE-2018-16850
See https://www.postgresql.org/about/news/1905/ for release information. Fixes CVE-2018-16850
See https://www.postgresql.org/about/news/1905/ for release information. Fixes CVE-2018-16850
See https://www.postgresql.org/about/news/1905/ for release information. Fixes CVE-2018-16850
lsix
force-pushed
the
update_postgresql
branch
from
528978f to
3cbc20e
Compare
c0bw3b
approved these changes
Nov 9, 2018
|
Success on x86_64-linux (full log) Attempted: postgresql_10, postgresql_11, postgresql_9_3, postgresql_9_4, postgresql_9_5, postgresql_9_6 Partial log (click to expand)
|
|
Success on aarch64-linux (full log) Attempted: postgresql_10, postgresql_11, postgresql_9_3, postgresql_9_4, postgresql_9_5, postgresql_9_6 Partial log (click to expand)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation for this change
There have been a release for all the supported postgresql versions.
See https://www.postgresql.org/about/news/1905/ for release information.
Fixes CVE-2018-16850
Once merged, I’ll port those updates to
release-18.03andrelease-18.09.Things done
sandboxinnix.confon non-NixOS)nix-shell -p nox --run "nox-review wip"./result/bin/)nix path-info -Sbefore and after)