Alexey Kondratov 13e8105740 feat(compute): Allow specifying the reconfiguration concurrency (#10006) ...

## Problem

We need a higher concurrency during reconfiguration in case of many DBs,
but the instance is already running and used by the client. We can
easily get out of `max_connections` limit, and the current code won't
handle that.

## Summary of changes

Default to 1, but also allow control plane to override this value for
specific projects. It's also recommended to bump
`superuser_reserved_connections` += `reconfigure_concurrency` for such
projects to ensure that we always have enough spare connections for
reconfiguration process to succeed.

Quick workaround for neondatabase/cloud#17846

2024-12-05 17:57:25 +00:00

..

src

feat(compute): Allow specifying the reconfiguration concurrency (#10006)

2024-12-05 17:57:25 +00:00

tests

Manage pgbouncer configuration from compute_ctl:

2023-12-26 15:17:09 +00:00

Cargo.toml

Remove unnecessary dependencies (#9000)

2024-09-17 17:55:45 +03:00