nixpkgs-ci[bot]
58e670273a
Merge master into staging-next
2025-05-08 00:16:38 +00:00
Wolfgang Walther
dc01def502
libpq: 17.14 -> 17.15
2025-05-07 20:31:41 +02:00
Wolfgang Walther
d7ea3c4fd4
postgresql_17: 17.4 -> 17.5
2025-05-07 20:10:12 +02:00
Wolfgang Walther
6de66bc0be
postgresql_16: 16.8 -> 16.9
2025-05-07 20:09:59 +02:00
Wolfgang Walther
4003ab6564
postgresql_15: 15.12 -> 15.13
2025-05-07 20:09:41 +02:00
Wolfgang Walther
43873fd4aa
postgresql_14: 14.17 -> 14.18
2025-05-07 20:09:20 +02:00
Wolfgang Walther
0552a5b5a9
postgresql_13: 13.20 -> 13.21
2025-05-07 20:08:59 +02:00
K900
f96ac2dcd6
Merge remote-tracking branch 'origin/master' into staging-next
2025-04-26 09:07:48 +03:00
Fernando Rodrigues
05580f4b44
treewide: switch instances of lib.teams.*.members to the new meta.teams attribute
...
Follow-up to #394797 .
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net >
2025-04-25 22:20:17 -03:00
K900
4acb251aaa
Merge remote-tracking branch 'origin/staging-next' into staging
2025-04-24 15:09:54 +03:00
Wolfgang Walther
28136b54b5
postgresqlPackages.timescaledb_toolkit: fix passthru tests
...
Missed the second reference to the VM tests in
e06b22b254
2025-04-24 10:18:11 +02:00
Wolfgang Walther
1a2cd3683e
postgresqlPackages: remove left-over nixosTests arguments
2025-04-24 10:17:17 +02:00
K900
df4847ebd5
Merge remote-tracking branch 'origin/staging-next' into staging
2025-04-22 21:21:57 +03:00
Maximilian Bosch
7a48cf7a02
Merge: postgresqlPackages: add "asserts" option to postgresqlTestExtensions ( #398205 )
2025-04-22 16:10:28 +02:00
K900
e22856305b
Merge remote-tracking branch 'origin/staging-next' into staging
2025-04-21 21:18:16 +03:00
Wolfgang Walther
faa7cc68e8
postgresqlPackages.timescaledb_toolkit: 1.19.0 -> 1.21.0 ( #400416 )
2025-04-21 12:55:44 +00:00
Wolfgang Walther
722e4bf4ff
postgresqlPackages.pgvecto-rs: move test from VM to postgresqlTestExtension
2025-04-21 12:56:19 +02:00
Wolfgang Walther
8ebdf33624
postgresqlPackages.postgis: use postgresqlTestExtension's asserts option
2025-04-21 12:36:30 +02:00
Wolfgang Walther
3af009b416
postgresqlPackages.tsja: move test from VM to postgresqlTestExtension
2025-04-21 12:36:26 +02:00
Wolfgang Walther
e06b22b254
postgresqlPackages.timescaledb: move test from VM to postgresqlTestExtension
2025-04-21 12:36:14 +02:00
Wolfgang Walther
6cc89cd16e
postgresqlPackages.citus: move test from VM to postgresqlTestExtension
2025-04-21 12:35:57 +02:00
Wolfgang Walther
debf86e09e
postgresqlPackages.rum: use postgresqlTestExtension helper
2025-04-21 12:34:51 +02:00
Wolfgang Walther
3ebdd4913c
postgresqlPackages.pg_byteamagic: improve tests with assertion
2025-04-21 12:34:46 +02:00
Wolfgang Walther
8d2b8de0a1
postgresqlPackages: add "asserts" option to postgresqlTestExtension
2025-04-21 12:34:43 +02:00
R. Ryantm
76cc55f630
postgresqlPackages.timescaledb_toolkit: 1.19.0 -> 1.21.0
2025-04-21 12:31:07 +02:00
R. Ryantm
8c739c788b
postgresqlPackages.timescaledb-apache: 2.19.2 -> 2.19.3
2025-04-21 03:16:55 +00:00
nixpkgs-ci[bot]
bd5d8282de
Merge staging-next into staging
2025-04-13 18:04:59 +00:00
Vladimír Čunát
a61952af35
staging-next 2025-04-03 ( #395862 )
2025-04-13 16:07:22 +02:00
Wolfgang Walther
4ad1a0ec67
postgresqlPackages: refactor finalAttrs support ( #398194 )
2025-04-13 12:31:53 +00:00
Diogo Correia
b50641edc8
postgresqlPackages: use finalAttrs pattern on cargo-pgrx extensions
2025-04-13 12:53:02 +01:00
Wolfgang Walther
052547291e
postgresqlPackages: use finalAttrs pattern where possible
2025-04-12 21:10:55 +02:00
Wolfgang Walther
54d293fc50
postgresqlPackages: use lib.extendMkDerivation in postgresqlBuildExtension
2025-04-12 21:05:30 +02:00
Wolfgang Walther
fee40ecec2
postgresql: add outputCheck for llvmPackages.llvm.lib
...
This should not leak into the out/lib outputs to keep the closure size
small.
2025-04-12 17:31:34 +02:00
nixpkgs-ci[bot]
a78b3ccf56
Merge staging-next into staging
2025-04-12 12:06:06 +00:00
nixpkgs-ci[bot]
de34ff9def
Merge master into staging-next
2025-04-12 12:05:35 +00:00
Wolfgang Walther
44060c6fc4
postgresqlPackages.pg-gvm: 22.6.8 -> 22.6.9 ( #398036 )
2025-04-12 11:53:20 +00:00
nixpkgs-ci[bot]
3bf50e95e8
Merge staging-next into staging
2025-04-12 00:15:51 +00:00
nixpkgs-ci[bot]
568e990505
Merge master into staging-next
2025-04-12 00:15:26 +00:00
R. Ryantm
369560e5b6
postgresqlPackages.pg-gvm: 22.6.8 -> 22.6.9
2025-04-11 23:28:07 +00:00
R. Ryantm
79f58ff6a2
postgresqlPackages.timescaledb-apache: 2.19.1 -> 2.19.2
2025-04-11 15:00:32 +00:00
nixpkgs-ci[bot]
9b0e9beb82
Merge staging-next into staging
2025-04-07 12:06:54 +00:00
K900
74d5b70eb2
Merge remote-tracking branch 'origin/master' into staging-next
2025-04-07 09:36:05 +03:00
Pol Dellaiera
f92efd3183
treewide: remove unneeded string interpolation
2025-04-07 08:08:12 +02:00
nixpkgs-ci[bot]
5c0edef29f
Merge staging-next into staging
2025-04-06 00:17:25 +00:00
K900
5e55028d84
Merge remote-tracking branch 'origin/master' into staging-next
2025-04-05 21:29:35 +03:00
Wolfgang Walther
9f3bea8dca
pkgsStatic.{libpq,postgresql}: fix linking against libpq.a
...
This can be observed when building
haskellPackages.postgresql-libpq-pkgconfig. This is currently pinned to
postgresql_16 in pkgsStatic, but when unpinning it, it will fail with
the mentioned error on master. With this fix, it successfully builds
with postgresql_17 / libpq.
2025-04-05 20:00:14 +02:00
Wolfgang Walther
dd5fd6cc22
postgresql: always build with JIT enabled
...
This changes the build to always enable JIT - but to only enable it at
run-time, when required. This keeps the runtime closure small without
JIT, but allows enabling it without a rebuild. We can do this, because
JIT is actually built as a shared module, which is loaded at run-time.
We put it into a -jit output and only link it into the environment when
requested.
Under the hood, this uses withPackages and adds the "JIT package" -
thus, to be able to use withPackages on top of that, we also need to be
able to apply withPackages repeatedly.
This cuts down the number of NixOS tests in half, because we don't need
to run it for every version with and without JIT anymore. There really
is no point in running everything with llvmjit.so in place, when the
queries are not making use of it anyway.
Also, we only need to build each extension once and not twice, further
reducing the number of rebuilds required for PRs touching postgresql.
2025-04-05 20:00:13 +02:00
Wolfgang Walther
dcb7a17994
pkgsMusl.postgresql_jit: disable tests
2025-04-05 20:00:10 +02:00
Wolfgang Walther
c0f7566ed5
postgresqlPackages.plv8: mark as broken on darwin
...
Darwin seems to be principially supported according to upstream's issue
tracker[1], but it fails to build. Thus marking as broken instead of
unsupported.
[1]: https://github.com/plv8/plv8/issues/303#issuecomment-424883342
2025-04-05 13:41:31 +02:00
Wolfgang Walther
cd972edfe4
postgresqlJitPackages.plv8: unbreak
...
This was originally marked as broken, because plv8 hardcoded gcc in its
Makefile. This has been resolved upstream in the meantime, so it builds
fine.
2025-04-05 13:41:30 +02:00
