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

..

ext

postgresqlTestHook: shutdown on failure

2025-05-11 10:44:20 +02:00

patches

…

13.nix

postgresql_13: 13.20 -> 13.21

2025-05-07 20:08:59 +02:00

14.nix

postgresql_14: 14.17 -> 14.18

2025-05-07 20:09:20 +02:00

15.nix

postgresql_15: 15.12 -> 15.13

2025-05-07 20:09:41 +02:00

16.nix

postgresql_16: 16.8 -> 16.9

2025-05-07 20:09:59 +02:00

17.nix

postgresql_17: 17.4 -> 17.5

2025-05-07 20:10:12 +02:00

default.nix

postgresql: always build with JIT enabled

2025-04-05 20:00:13 +02:00

ext.nix

…

generic.nix

postgresqlPackages: remove unused inputs

2025-05-11 10:44:16 +02:00

libpq.nix

Merge remote-tracking branch 'origin/master' into staging-next

2025-04-26 09:07:48 +03:00

pg_config.env.mk

…

pg_config.nix

postgresql.pg_config: add check to confirm output is correct

2025-03-23 20:40:37 +01:00

pg_config.sh

…

postgresqlBuildExtension.nix

staging-next 2025-04-03 (#395862)

2025-04-13 16:07:22 +02:00

postgresqlTestExtension.nix

postgresqlTestHook: shutdown on failure

2025-05-11 10:44:20 +02:00