New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update all supported postgresql versions (Fixes CVE-2018-16850) #49906
Conversation
postgresql-10 (and less probable postgresql-11) users using |
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)
|
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... |
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. |
Maybe this should target |
55199fb
to
528978f
Compare
@c0bw3b I have just rebased to staging a changed the PR's base. |
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
528978f
to
3cbc20e
Compare
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)
|
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.03
andrelease-18.09
.Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)