postgresql: 13.17 -> 13.18, 14.14 -> 14.15, 15.9 -> 15.10, 16.5 -> 16.6, 17.1 -> 17.2

[wolfgangwalther]

New PostgreSQL minor versions released: https://www.postgresql.org/about/news/postgresql-172-166-1510-1415-1318-and-1222-released-2965/

There are no critical changes, so targeting staging for all of them at the same time.

Also see #355965 (comment) for the reason for those new versions so quickly after the last ones.

This is very unlikely to break anything.

Things done

• Built on platform(s)
  • x86_64-linux (on master, without JIT, no extensions)
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[github-actions]

Backport failed for staging-24.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin staging-24.05
git worktree add -d .worktree/backport-358213-to-staging-24.05 origin/staging-24.05
cd .worktree/backport-358213-to-staging-24.05
git switch --create backport-358213-to-staging-24.05
git cherry-pick -x 41dcc3c9746d282181c08b7531ff486b5fbe13f2 3aa011583b3e362b63f468da2f54953fa289f8c7 256921e7d3f563376e3eaf44328a65a67181e988 f4ef8018ac170ca6dad34b354bfcd5ab91037a7d 6aa3d742421e9ea74a91965e14a4eb760e789e58

[github-actions]

Successfully created backport PR for staging-24.11:

• [Backport staging-24.11] postgresql: 13.17 -> 13.18, 14.14 -> 14.15, 15.9 -> 15.10, 16.5 -> 16.6, 17.1 -> 17.2 #358377

[wolfgangwalther]

Backport failed for staging-24.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin staging-24.05
git worktree add -d .worktree/backport-358213-to-staging-24.05 origin/staging-24.05
cd .worktree/backport-358213-to-staging-24.05
git switch --create backport-358213-to-staging-24.05
git cherry-pick -x 41dcc3c9746d282181c08b7531ff486b5fbe13f2 3aa011583b3e362b63f468da2f54953fa289f8c7 256921e7d3f563376e3eaf44328a65a67181e988 f4ef8018ac170ca6dad34b354bfcd5ab91037a7d 6aa3d742421e9ea74a91965e14a4eb760e789e58

@Ma27 are you going to create the backport or should I?

[Ma27]

Will do this afternoon. Kinda crowded review queue here :D