Skip to content
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

postgresql: 9.5.20 -> 9.5.21, 9.6.16 -> 9.6.17, 10.11 -> 10.12, 11.6 -> 11.7, 12.1 -> 12.2 #80328

Merged
merged 5 commits into from Feb 18, 2020

Conversation

marsam
Copy link
Contributor

@marsam marsam commented Feb 17, 2020

Motivation for this change

https://www.postgresql.org/about/news/2011/

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@danbst
Copy link
Contributor

danbst commented Feb 17, 2020

I think we should not treat those as mass rebuilds, so no need to base on staging.

I recall someone told me it is fine to merge pg to master. But let's check that.

I took as an example one of previous CVE pg updates: #63601
I did backport to 19.03 on 2019-06-23.

Looking at Hydra, I found the evaluation which picked up my commit: https://hydra.nixos.org/eval/1526884?filter=&compare=1526814&full=#tabs-still-succeed
It lasted ~40 minutes and completed at 2019-06-23 21:55:30

Hydra eval had revision 8634c3b. We can then lookup when was 19.03 channel switched to that revision using an awesome @grahamc service https://channels.nix.gsc.io/nixos-19.03/history-v2

Indeed, there is a line

8634c3b619909db7fc747faf8c03592986626e21 1561092479 1561361411

Format is "commit-hash date-of-commit date-of-advancement". We don't care about date-of-commit, because it is not date of git push, but date-of-advancement is one when all builds were finished and channel advanced.

$ date -d @1561361411 --iso-8601=seconds
2019-06-24T10:30:11+03:00

So, comparing it to my backport push date, I conclude it took ~12 hours to rebuild all the Qt stuff which depends on postgresql (modulo non-adjusted timezone errors).

Is 12 hours a mass-rebuild? I have vague memories that threshold is 3 days, but cc @vcunat as knowledge bearer and potentially interested (#19045)

Copy link
Member

@lsix lsix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Built and tested using nixos/tests/postgis.nix and nixos/tests/postgresql.nix.

All fine for me.

Thanks.

@danbst danbst merged commit 036c524 into NixOS:staging Feb 18, 2020
@danbst
Copy link
Contributor

danbst commented Feb 18, 2020

pushed release-19.09 34becef..847bf0b
pushed release-20.03 2197162..ed7f18b

vcunat pushed a commit that referenced this pull request Feb 18, 2020
Forward-picked from merge 036c524 in staging to master,
as upstream claims it fixes CVE-2020-1720.
https://www.postgresql.org/about/news/2011/
@vcunat
Copy link
Member

vcunat commented Feb 18, 2020

My understanding is that there's a security issue fixed and Hydra's currently not much loaded, so in that light the rebuild certainly doesn't seem large, and I also picked this to master in 329102c.

@danbst
Copy link
Contributor

danbst commented Feb 18, 2020

@vcunat how many hours is "large"? Do we have ETA on channel advancement?

Also, are there historical graphs of "hydra much loaded"?

@vcunat
Copy link
Member

vcunat commented Feb 18, 2020

IIRC @grahamc has shown some graphs, but I can't find any URL now (except for OfBorg). There's certainly no hard limit what's large – for me it's mainly intuitive estimate; the counts of rebuilds also aren't perfect in the sense that they don't easily translate into e.g. those "hours" of Hydra work. It also depends on urgency of the change and its likelihood to break things – mass rebuilds sometimes get slowed down not just due to rebuilds but also due to mass breakages.

@danbst
Copy link
Contributor

danbst commented Feb 18, 2020

@vcunat thanks. Hadn't thought about mass breakages.

@vcunat
Copy link
Member

vcunat commented Feb 19, 2020

I found the Hydra graphs: https://status.nixos.org/grafana/?orgId=1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants