summaryrefslogtreecommitdiff
path: root/pkgs/servers/sql/postgresql/generic.nix (follow)
Commit message (Expand)AuthorAgeFilesLines
* Merge: postgresql.pg_config: add check to confirm output is correct (#392418)Maximilian Bosch2025-03-301-1/+7
|\
| * postgresql.pg_config: add check to confirm output is correct•••This is only tested on native builds against the output of the original pg_config, which should be enough. Wolfgang Walther2025-03-231-1/+7
* | Merge staging-next into stagingnixpkgs-ci[bot]2025-03-251-5/+8
|\ \ | |/ |/|
| * postgresql: simplify doInstallCheck condition and fix commentsWolfgang Walther2025-03-231-5/+8
* | Merge staging-next into stagingnixpkgs-ci[bot]2025-03-221-2/+3
|\|
| * postgresql: drop tests on aarch64-darwin, too•••I don't know. No progress in sight. Let's at least unblock all those dependees. Vladimír Čunát2025-03-221-2/+3
* | postgresql: provide PL/Perl, PL/Python and PL/Tcl as packages (#385859)Wolfgang Walther2025-03-211-43/+99
|\ \
| * | postgresql: provide pltcl extension as package•••This allows us to always build the extension, but still have the user explicitly enable it without causing rebuilds. Wolfgang Walther2025-03-211-3/+19
| * | postgresql: provide plperl extension as package•••This allows us to always build the extension, but still have the user explicitly enable it without causing rebuilds. Wolfgang Walther2025-03-211-9/+22
| * | postgresql: provide plpython3 extension as package•••This allows us to always build the extension, but still have the user explicitly enable it without causing rebuilds. Wolfgang Walther2025-03-211-15/+38
| * | postgresql: fix tclSupport with strictDeps•••Can't find tcl anymore ever since we enabled strictDeps. Need to do the same as for perl and python. Wolfgang Walther2025-03-211-2/+2
| * | postgresql: fix cross-compilation with perlSupport•••Perl is available in nativeBuildInputs, but the perl used at runtime, must be a different one. Thus, we need to explicitly tell configure about it, similar to how we did with python. Wolfgang Walther2025-03-211-10/+13
| * | postgresql: remove left-over buildInput python•••We don't need to pass it as build input anymore, because we pass it via PYTHON environment variable already. Wolfgang Walther2025-03-211-1/+0
| * | postgresql: switch to makeBinaryWrapper•••This could be slightly faster and since "postgres" is called for every connection, it could theoretically make a difference with high throughput. Wolfgang Walther2025-03-211-2/+2
| * | postgresql: disable unconditional plperl in versions before 17•••We accidentally enabled building plperl in versions before 17 unconditionally, which was not intended. Happened in be8612e15a2849936faf954d46da0d29e3f2c24e. Wolfgang Walther2025-03-211-1/+1
| * | postgresql: use lib.getExeWolfgang Walther2025-03-211-1/+1
| * | postgresql: use meta.availableOn for linux-pamWolfgang Walther2025-03-211-5/+7
| * | postgresql: move CFLAGS comment•••This only applies to CFLAGS, not all of env. Wolfgang Walther2025-03-211-5/+5
* | | postgresql: replace pg_config with custom script•••By replacing upstream's pg_config binary with a shell script, we: - gain the ability to run pg_config easily when cross-compiling, - can remove the fake pg_config in the default output, - can remove the pg_config wrapper script dealing with special cases. Some 20 years ago, pg_config *was* a shell script upstream, too. It was changed to a binary, when it was made "relocatable", so it would return paths depending on the location of the "postgres" binary. However, this is exactly the thing that just hurts us in nixpkgs - we don't want those paths to change, we want them to always point at the right outputs. By writing the script ourselves, this becomes a lot less painful. This approach means more lines of codes, but all of them are dead simple and we have a lot less complexity overall. Additionally, pg_config is now made a separate derivation, only exposed as "postgresql.pg_config". This has the nice side-effect, that all users of postgresql and libpq in nixpkgs must be very *explicit* about their dependency on pg_config. This gives a lot more visibility into the state of affairs regarding pkg-config support for libpq, which ultimately is the much better solution. Wolfgang Walther2025-03-211-10/+8
|/ /
* | Merge staging-next into stagingnixpkgs-ci[bot]2025-03-181-29/+3
|\|
| * postgresql: split postgresqlTestExtension into separate fileWolfgang Walther2025-03-181-27/+1
| * postgresqlPackages: rename buildPostgresqlExtension to postgresqlBuildExtension•••This is for consistency with postgresqlTestExtension and postgresqlTestHook. Everything that is passed via postgresql's generic.nix "packages scope" now is prefixed with "postgresql". Wolfgang Walther2025-03-181-1/+1
| * postgresqlPackages: load automatically from ext/ folder•••No need to manually put them in the default.nix file anymore. Wolfgang Walther2025-03-181-1/+1
* | postgresql: remove unused argument•••Accidentally introduced in 247053e. Wolfgang Walther2025-03-161-1/+0
* | postgresql: fix cross for FreeBSD•••- Fix dependencies (uuid and locale) - Add the --export-dynamic flag - it is applicable for all autotools-based cross configurations starting with v16. Audrey Dutcher2025-03-141-2/+21
|/
* postgresql_13: 13.18 -> 13.20•••ChangeLog: https://www.postgresql.org/about/news/postgresql-173-167-1511-1416-and-1319-released-3015/ https://www.postgresql.org/about/news/out-of-cycle-release-scheduled-for-february-20-2025-3016/ Co-authored-by: Wolfgang Walther <walther@technowledgy.de> Maximilian Bosch2025-02-181-5/+0
* postgresql: fetch from GitHub instead of tarball•••This allows us to fetch newer releases a few days before they are officially released and the tarballs have been pushed. The regular release cycle is like this: - Sunday, the release notes are committed. - Monday, the version is "stamped", i.e. the version bump committed. - Thursday, the release is made. There are not going to be any changes from Monday on, so we can kick off our builds at that time already - they still need time to hit unstable anyway. Wolfgang Walther2025-02-181-11/+14
* various: replace substituteAll with replaceVars•••Some easy ones. Wolfgang Walther2025-01-261-3/+2
* postgresql: fix build•••The recent tzdata update to 2025a broke postgres' test suite. Until the next minor releases come out, we'll apply upstream's commit to fix this as a patch. Wolfgang Walther2025-01-211-0/+5
* Merge staging-next into stagingnixpkgs-ci[bot]2025-01-181-7/+13
|\
| * Merge master into staging-nextnixpkgs-ci[bot]2025-01-181-7/+13
| |\
| | * postgresql: add PYTHONPATH via wrapProgram•••Currently `PYTHONPATH` is not set when building PostgreSQL. This results in Python modules not being available within `pl/python3u`. This commit adds `PYTHONPATH` of the supplied `python3` via `wrapProgram`, which is especially useful when supplying a custom Python env. Christoph Hrdinka2025-01-151-4/+8
| | * postgresql: fix build if pythonSupport is enabled•••Since https://github.com/NixOS/nixpkgs/commit/445371f309a62e9107ad78fb3c65fff768efb43c (which added `strictDeps = true;`) the build of PostgreSQL is broken if python support is enabled (via argument `pythonSupport = true`). The problem seems to be that PostgreSQL’s build system is unable to find the supplied Python installation. This commit fixes the build by setting the `PYTHON` environment variable within the build environment, as document here: https://www.postgresql.org/docs/current/install-make.html#CONFIGURE-ENVVARS-PYTHON Closes #372333 Christoph Hrdinka2025-01-101-3/+5
* | | postgresql: fix build on x86_64-darwin (#371534)Wolfgang Walther2025-01-071-2/+8
|\ \ \ | |/ / |/| |
| * | postgresql: fix build on x86_64-darwin•••Resolves #371242 Wolfgang Walther2025-01-061-2/+8
| |/
* / postgresql: add doc/man outputChecks for all versions•••See a0919c7eeda731b1f8e2948d9feebb4ad9b89aab for rationale. Wolfgang Walther2025-01-041-42/+39
|/
* postgresql_14: fix build•••Building postgresql_14 currently fails with this on master: error: derivation contains an illegal reference specifier 'man' The reason seems to be a bug in nix, where outputChecks are run improperly when one of the outputs can already be substituted. Why the man output can be substituted from hydra is unknown, but adding more outputChecks for the the man and doc outputs should work around the problem until nix is fixed. Wolfgang Walther2025-01-021-23/+45
* Merge master into staging-nextgithub-actions[bot]2024-12-231-0/+3
|\
| * various: fix hostPlatform.canExecute buildPlatform•••It doesn't matter whether the hostPlatform could execute stuff from the buildPlatform - we need it the other way around: Certain things during a build process can only happen when, as part of the build, the **buildPlatform** can execute the code it just created for the **hostPlatform**. Unless we are talking about compilation at run-time, as in the case of PostgreSQL. Extend the comment there to make it clear that this is on purpose. Another case that's OK is vlc, where luac can't cross-compile at build time, thus the bytecode is actually build for the buildPlatform and the sources must be interpreted at runtime instead. Wolfgang Walther2024-12-221-0/+3
| * treewide: format all inactive Nix files•••After final improvements to the official formatter implementation, this commit now performs the first treewide reformat of Nix files using it. This is part of the implementation of RFC 166. Only "inactive" files are reformatted, meaning only files that aren't being touched by any PR with activity in the past 2 months. This is to avoid conflicts for PRs that might soon be merged. Later we can do a full treewide reformat to get the rest, which should not cause as many conflicts. A CI check has already been running for some time to ensure that new and already-formatted files are formatted, so the files being reformatted here should also stay formatted. This commit was automatically created and can be verified using nix-build https://github.com/infinisil/treewide-nixpkgs-reformat-script/archive/a08b3a4d199c6124ac5b36a889d9099b4383463f.tar.gz \ --argstr baseRev b32a0943687d2a5094a6d92f25a4b6e16a76b5b7 result/bin/apply-formatting $NIXPKGS_PATH Silvan Mosberger2024-12-101-277/+387
| * postgresql: drop build-time dependency on GHC•••This replaces `writeShellApplication` with `writeShellScriptBin` that doesn't perform a shellcheck. This makes it way easier to build postgresql on staging since GHC is super slow to build, even with pretty powerful machines. Also Haskell updates are currently merged straight into master which means that postgresql and all reverse dependencies require a rebuild on master then[1]. [1] https://github.com/NixOS/nixpkgs/pull/354270#issuecomment-2463196665 (cherry picked from commit 4cd083a3cdf25fce6d1c0bb232e241681fad34ca) (cherry picked from commit a40d887561d5f4a6d330181891d78174f82e84e4) Maximilian Bosch2024-11-301-5/+2
| * postgresql_16: 16.4 -> 16.5•••Release Notes: https://www.postgresql.org/about/news/postgresql-171-165-159-1414-1317-and-1221-released-2955/ (cherry picked from commit 797b544bda2f9b921c9757c422aa68a1de1b431b) (cherry picked from commit 77ea13f37774efb6360729f03767ef72b1333e4f) Wolfgang Walther2024-11-301-7/+0
* | treewide: format all inactive Nix files•••After final improvements to the official formatter implementation, this commit now performs the first treewide reformat of Nix files using it. This is part of the implementation of RFC 166. Only "inactive" files are reformatted, meaning only files that aren't being touched by any PR with activity in the past 2 months. This is to avoid conflicts for PRs that might soon be merged. Later we can do a full treewide reformat to get the rest, which should not cause as many conflicts. A CI check has already been running for some time to ensure that new and already-formatted files are formatted, so the files being reformatted here should also stay formatted. This commit was automatically created and can be verified using nix-build https://github.com/infinisil/treewide-nixpkgs-reformat-script/archive/a08b3a4d199c6124ac5b36a889d9099b4383463f.tar.gz \ --argstr baseRev 78e9caf153f5a339bf1d4c000ff6f0a503a369c8 result/bin/apply-formatting $NIXPKGS_PATH Silvan Mosberger2024-12-101-343/+422
* | postgresql: remove libxml http workaroundIvan Mincik2024-12-091-1/+1
* | Merge: pkgsStatic.postgresql: fix build (#345289)Maximilian Bosch2024-12-011-7/+18
|\ \
| * | postgresql: add -export_dynamic on darwin only for v16Wolfgang Walther2024-11-301-3/+2
| * | pkgsStatic.postgresql: fix build•••The underlying problem was fixed as a side-effect of [1], for reasons unknown to me. In the current state, it's enough to disable a few breaking dependencies to make the build pass. Note, that this builds the full package, including backend. However, the backend is not working, yet: Loading shared modules, which PostgreSQL heavily depends is still broken. Further, all binaries in the default output, even client binaries such as psql, are currently dynamically linked against libpq.so. While the current autoconf based build system doesn't support changing this, this might be possible in the future with meson. However, not all is bad: Fixing the build allows using the static libpq.a library, which is probably the one thing that most users want from pkgsStatic.postgresql anyway. Resolves #191920 [1]: 77977286d80c9bfb77cbf80989d41c59d66dccf8 Wolfgang Walther2024-11-301-4/+13
| * | postgresql: enable strictDepsWolfgang Walther2024-11-301-0/+3
* | | stdenv.mkDerivation: avoid depending on derivations passed in outputChecks•••This was added for non-structuredAttrs output checks in #211783. Here we extend the same concept to structuredAttrs-enabled outputChecks, too. The postgresql package worked around this with some conditionals. Those can now be removed - without causing LLVM to be built or substituted. Wolfgang Walther2024-11-251-6/+4
|/ /
* | Merge: postgresql: fix pgxs Makefile for darwin (#358566)Maximilian Bosch2024-11-241-0/+6
|\ \
generated by cgit v1.2.3 (git 2.52.0) at 2026-01-17 17:12:28 +0000