4 people a569501108 chore(test): set connection lifetimes for postgresql (#8586) ...

# Which Problems Are Solved

defaults.yaml only specifies defaults for cockroach. Therefore, options
omitted for postgresql are actually set to `0`.
This means that the connections timeouts are set to `0` and connections
were not reused, resulting in a performance penalty while running the
integration tests.

# How the Problems Are Solved

Set MaxConnLifeTime and MaxConnIdleTime options in postgres


# Additional Changes

- none

# Additional Context

- none

Co-authored-by: Silvan <[email protected]>
Co-authored-by: Livio Spring <[email protected]>

2024-09-11 07:45:02 +00:00

..

config

chore(test): set connection lifetimes for postgresql (#8586)

2024-09-11 07:45:02 +00:00

sink

chore(tests): use a coverage server binary (#8407)

2024-09-06 14:47:57 +02:00

assert_test.go

feat: impersonation roles (#7442)

2024-02-28 10:21:11 +00:00

assert.go

chore(tests): use a coverage server binary (#8407)

2024-09-06 14:47:57 +02:00

client.go

chore(tests): use a coverage server binary (#8407)

2024-09-06 14:47:57 +02:00

config.go

chore(tests): use a coverage server binary (#8407)

2024-09-06 14:47:57 +02:00

instance.go

chore(tests): use a coverage server binary (#8407)

2024-09-06 14:47:57 +02:00

oidc.go

chore(tests): use a coverage server binary (#8407)

2024-09-06 14:47:57 +02:00

rand.go

feat: restrict languages (#6931)

2023-12-05 11:12:01 +00:00

system.go

chore(tests): use a coverage server binary (#8407)

2024-09-06 14:47:57 +02:00

user.go

chore(tests): use a coverage server binary (#8407)

2024-09-06 14:47:57 +02:00

usertype_enumer.go

chore(tests): use a coverage server binary (#8407)

2024-09-06 14:47:57 +02:00