postgresqlPackages.pg_tle: init at 1.4.0

[BenChand]

Things done

Tested as an extension in private repo on aarch64-linux and aarch64-darwin

• Built on platform(s)
  • x86_64-linux
  • 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.

[wolfgangwalther]

High-level question, but not blocking:

This extension allows installing more extensions non-declaratively...

... is this really what we want in the context of nixpkgs? Somehow our goal is the exact opposite, right?

[BenChand]

High-level question, but not blocking:

This extension allows installing more extensions non-declaratively...

... is this really what we want in the context of nixpkgs? Somehow our goal is the exact opposite, right?

I'm not too sure what the best approach would be but I can outline my use-case - I'm working with a private postgres extension that is build outside of the nix ecosystem and is installed via pg_tle. I want to run integration tests through nix which requires spinning up a postgres instance during the build process, which requires the pg_tle extension to be present. If it's not suitable for nixpkgs I can close.

[wolfgangwalther]

I'm not too sure what the best approach would be but I can outline my use-case - I'm working with a private postgres extension that is build outside of the nix ecosystem and is installed via pg_tle. I want to run integration tests through nix which requires spinning up a postgres instance during the build process, which requires the pg_tle extension to be present.

Yeah, makes sense. You could always package this extension up for nix in a private overlay, but this wouldn't help for integration testing with pg_tle.

If it's not suitable for nixpkgs I can close.

It is, no worries - as I said: non-blocking. All pg extensions are suitable for nixpkgs, imho.

[wolfgangwalther]

Please squash all the commits into the first one, too.

[wolfgangwalther]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 387868

---

x86_64-linux

✅ 10 packages built:

• postgresql13JitPackages.pg_tle
• postgresql13Packages.pg_tle
• postgresql14JitPackages.pg_tle
• postgresql14Packages.pg_tle
• postgresql15JitPackages.pg_tle
• postgresql15Packages.pg_tle
• postgresql16JitPackages.pg_tle
• postgresql16Packages.pg_tle
• postgresqlJitPackages.pg_tle (postgresql17JitPackages.pg_tle)
• postgresqlPackages.pg_tle (postgresql17Packages.pg_tle)

---

aarch64-linux

✅ 10 packages built:

• postgresql13JitPackages.pg_tle
• postgresql13Packages.pg_tle
• postgresql14JitPackages.pg_tle
• postgresql14Packages.pg_tle
• postgresql15JitPackages.pg_tle
• postgresql15Packages.pg_tle
• postgresql16JitPackages.pg_tle
• postgresql16Packages.pg_tle
• postgresqlJitPackages.pg_tle (postgresql17JitPackages.pg_tle)
• postgresqlPackages.pg_tle (postgresql17Packages.pg_tle)

---

x86_64-darwin

✅ 10 packages built:

• postgresql13JitPackages.pg_tle
• postgresql13Packages.pg_tle
• postgresql14JitPackages.pg_tle
• postgresql14Packages.pg_tle
• postgresql15JitPackages.pg_tle
• postgresql15Packages.pg_tle
• postgresql16JitPackages.pg_tle
• postgresql16Packages.pg_tle
• postgresqlJitPackages.pg_tle (postgresql17JitPackages.pg_tle)
• postgresqlPackages.pg_tle (postgresql17Packages.pg_tle)

---

aarch64-darwin

✅ 10 packages built:

• postgresql13JitPackages.pg_tle
• postgresql13Packages.pg_tle
• postgresql14JitPackages.pg_tle
• postgresql14Packages.pg_tle
• postgresql15JitPackages.pg_tle
• postgresql15Packages.pg_tle
• postgresql16JitPackages.pg_tle
• postgresql16Packages.pg_tle
• postgresqlJitPackages.pg_tle (postgresql17JitPackages.pg_tle)
• postgresqlPackages.pg_tle (postgresql17Packages.pg_tle)

[wolfgangwalther]

Thanks!