Commit Graph

1416 Commits

Author SHA1 Message Date
R. Ryantm
53b89aca2b postgresqlPackages.omnigres: 0-unstable-2025-06-03 -> 0-unstable-2025-06-27 2025-07-03 15:17:39 +00:00
Diogo Correia
ab82f5a511 postgresqlPackages.vectorchord: init at 0.4.2 2025-07-02 13:36:52 +01:00
Wolfgang Walther
f307abef1e postgresql.withPackages.pg_config: fix paths (#419486) 2025-06-27 14:38:44 +00:00
Diogo Correia
40c358076c postgresqlPackages.{pgvectorscale,pgx_ulid}: pin cargo-pgrx 0.12.6 2025-06-26 18:40:36 +01:00
R. Ryantm
a580f7e5f0 postgresqlPackages.pg_net: 0.15.1 -> 0.16.0 2025-06-26 10:41:58 +00:00
R. Ryantm
82dbe793af postgresqlPackages.h3-pg: 4.2.2 -> 4.2.3 2025-06-24 20:54:11 +00:00
Wolfgang Walther
9a146d1244 postgresql.withPackages.pg_config: fix paths
Previously, pg_config would report the paths of the underlying
postgresql derivation and not the paths of the buildEnv that
postgresql.withPackages creates.

That's a problem when users of pg_config use it to find PostgreSQL's
sharedir, in which they'd like to find the extensions added via
withPackages. Those are only linked into the created buildEnv, but not
available in the postgresql derivation.

By providing our own nix-support/pg_config.env file, we can swap out
those paths. We also do the same for the -man output, because this
output is linked into buildEnv as well. Other paths, which are not
available in the buildEnv environment, will still link to the original
postgresql derivation. Win-win!
2025-06-24 10:01:07 +02:00
Luke Granger-Brown
a013d9258c nixos/nipap: init 2025-06-23 21:52:32 +01:00
Luke Granger-Brown
5a0374e20e postgresqlPackages.ip4r: init at 2.4.2 2025-06-23 00:12:13 +01:00
Wolfgang Walther
6c455620b3 postgresqlPackages.timescaledb: fix passthru tests
timescaledb_toolkit never was a library to be preloaded anyway, it must
have found its way in there by accident. The extension is created via
CREATE EXTENSION, and that's enough for the test to pass.

The reason this fails is, because a recent commit changed the way the
timescaledb_toolkit.so library is created - it now carries a version
number, which makes PostgreSQL not able to find it.
2025-06-12 14:10:21 +02:00
Wolfgang Walther
eb29e816c5 postgresqlPackages.timescaledb: 2.20.2 -> 2.20.3 (#415941) 2025-06-12 10:21:23 +00:00
R. Ryantm
694c438105 postgresqlPackages.timescaledb: 2.20.2 -> 2.20.3 2025-06-11 19:55:14 +00:00
WilliButz
356d4fc91c treewide: remove myself from maintainers
This removes maintainer entries which haven't reflected reality for a
while, mostly due to a change in focus towards other topics.
2025-06-11 17:39:42 +02:00
syvb
4183008322 postgresqlPackages.timescaledb_toolkit: run post-install script 2025-06-09 20:22:58 -04:00
Wolfgang Walther
435b64d298 postgresqlPackages.omnigres: 0-unstable-2025-05-16 -> 0-unstable-2025-06-03 (#414586) 2025-06-09 13:14:59 +00:00
Marcos Benevides
d6b530cc9c postgresqlPackages.omnigres: 0-unstable-2025-05-16 -> 0-unstable-2025-06-03
---------

Co-authored-by: Wolfgang Walther <walther@technowledgy.de>
2025-06-09 08:59:50 -04:00
R. Ryantm
b6286021a2 postgresqlPackages.timescaledb-apache: 2.20.1 -> 2.20.2 2025-06-07 22:58:08 +00:00
R. Ryantm
8308f5ed6a postgresqlPackages.pg_net: 0.14.0 -> 0.15.1 2025-06-07 15:57:10 +00:00
R. Ryantm
ae47547b26 postgresqlPackages.pg_ivm: 1.10 -> 1.11 2025-05-29 01:46:41 +00:00
R. Ryantm
2ed3d93854 postgresqlPackages.timescaledb-apache: 2.20.0 -> 2.20.1 2025-05-27 22:16:42 +00:00
Marcos Benevides
c4381dafbc omnigres: init at 0-unstable-2025-05-16
---------

Co-authored-by: Wolfgang Walther <walther@technowledgy.de>
Co-authored-by: Yurii Rashkovskii <yrashk@gmail.com>
2025-05-20 07:19:12 -04:00
Wolfgang Walther
867c07c1b6 postgresqlPackages.pg_tle: 1.5.0 -> 1.5.1 (#407257) 2025-05-16 20:26:12 +00:00
R. Ryantm
71ae3ddcb0 postgresqlPackages.timescaledb-apache: 2.19.3 -> 2.20.0 2025-05-16 20:08:34 +10:00
R. Ryantm
6b52d2e642 postgresqlPackages.pg_tle: 1.5.0 -> 1.5.1 2025-05-15 06:07:48 +00:00
Nikolay Korotkiy
55116ee2c8 postgresqlPackages.pgrouting: 3.7.3 → 3.8.0 2025-05-11 17:07:12 +04:00
Wolfgang Walther
065fefd975 postgresqlTestHook: shutdown on failure
Previously, the user of postgresqlTestHook would have needed to set
failureHook accordingly. However, this was not a clean solution, because
postgresqlStop would also run for configure or build failures, before
the server was even started. This gave odd errors from a failed shutdown
in the log.

Now postgresqlStop is only called when it makes sense - and whenever
postgresqlTestHook is used.
2025-05-11 10:44:20 +02:00
Wolfgang Walther
e1573ae30b postgresqlPackages: remove unused inputs
Thanks, deadnix.
2025-05-11 10:44:16 +02:00
K900
578c3f18a7 postgis: backport patch to fix tests with GDAL 3.11 2025-05-10 16:45:38 +03: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